linux.git/fs/sysv/inode.c, branch v2.6.37

sysv: do not mark superblock dirty on remount

2010-08-09T20:48:58+00:00

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 
Signed-off-by: Al Viro

switch sysv to ->evict_inode()

2010-08-09T20:47:59+00:00

Signed-off-by: Al Viro

fix fs/sysv s_dirt handling

2010-05-28T02:16:05+00:00

got broken on ->sync_fs() conversion a year ago, nobody noticed...

Signed-off-by: Al Viro

pass writeback_control to ->write_inode

2010-03-05T18:25:52+00:00

This gives the filesystem more information about the writeback that
is happening.  Trond requested this for the NFS unstable write handling,
and other filesystems might benefit from this too by beeing able to
distinguish between the different callers in more detail.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

get rid of BKL in fs/sysv

2009-06-17T04:36:37+00:00

Signed-off-by: Al Viro

sysv: add ->sync_fs

2009-06-12T01:36:16+00:00

Add a ->sync_fs method for data integrity syncs, and reimplement
->write_super ontop of it.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

repair sysv_write_inode(), switch sysv to simple_fsync()

2009-06-12T01:36:12+00:00

Signed-off-by: Al Viro

->write_super lock_super pushdown

2009-06-12T01:36:09+00:00

Push down lock_super into ->write_super instances and remove it from the
caller.

Following filesystem don't need ->s_lock in ->write_super and are skipped:

 * bfs, nilfs2 - no other uses of s_lock and have internal locks in
	->write_super
 * ext2 - uses BKL in ext2_write_super and has internal calls without s_lock
 * reiserfs - no other uses of s_lock as has reiserfs_write_lock (BKL) in
 	->write_super
 * xfs - no other uses of s_lock and uses internal lock (buffer lock on
	superblock buffer) to serialize ->write_super.  Also xfs_fs_write_super
	is superflous and will go away in the next merge window

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

Push lock_super() into the ->remount_fs() of filesystems that care about it

2009-06-12T01:36:08+00:00

Note that since we can't run into contention between remount_fs and write_super
(due to exclusion on s_umount), we have to care only about filesystems that
touch lock_super() on their own.  Out of those ext3, ext4, hpfs, sysv and ufs
do need it; fat doesn't since its ->remount_fs() only accesses assign-once
data (basically, it's "we have no atime on directories and only have atime on
files for vfat; force nodiratime and possibly noatime into *flags").

[folded a build fix from hch]

Signed-off-by: Al Viro

push BKL down into ->put_super

2009-06-12T01:36:07+00:00

Move BKL into ->put_super from the only caller.  A couple of
filesystems had trivial enough ->put_super (only kfree and NULLing of
s_fs_info + stuff in there) to not get any locking: coda, cramfs, efs,
hugetlbfs, omfs, qnx4, shmem, all others got the full treatment.  Most
of them probably don't need it, but I'd rather sort that out individually.
Preferably after all the other BKL pushdowns in that area.

[AV: original used to move lock_super() down as well; these changes are
removed since we don't do lock_super() at all in generic_shutdown_super()
now]
[AV: fuse, btrfs and xfs are known to need no damn BKL, exempt]

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro