android_kernel_xiaomi_sm8350/fs/sysv
Artem Bityutskiy 719f2c879f sysv: do not mark superblock dirty on remount
No need to mark the superblock as dirty in sysv_remount, synchronize
it instead (only if mounting R/O).

I did not find any docs about this file-system, and I have no possibility
to test my changes. Thus, this is untested. I see other issues in sysv,
e.g., why sysv_sync_fs writes only in the FSTYPE_SYSV4 case? However,
it marks its SB bh's dirty for all types, and does not wait for them
ever. With zero docs I'm unable to fix this.

Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-09 16:48:58 -04:00
..
balloc.c
dir.c clean up write_begin usage for directories in pagecache 2010-08-09 16:47:31 -04:00
file.c remove inode_setattr 2010-08-09 16:47:37 -04:00
ialloc.c switch sysv to ->evict_inode() 2010-08-09 16:47:59 -04:00
inode.c sysv: do not mark superblock dirty on remount 2010-08-09 16:48:58 -04:00
itree.c get rid of block_write_begin_newtrunc 2010-08-09 16:47:33 -04:00
Kconfig fs/Kconfig: move sysv out 2009-01-22 13:15:59 +03:00
Makefile
namei.c constify dentry_operations: misc filesystems 2009-03-27 14:44:00 -04:00
super.c sysv: do not mark superblock dirty on mount 2010-08-09 16:48:56 -04:00
symlink.c [PATCH] mark struct inode_operations const 3 2007-02-12 09:48:46 -08:00
sysv.h clean up write_begin usage for directories in pagecache 2010-08-09 16:47:31 -04:00