user/sven/linux.git/fs/internal.h, branch v3.4.85

vfs: protect remounting superblock read-only

2012-01-07T04:20:12Z

Currently remouting superblock read-only is racy in a major way. With the per mount read-only infrastructure it is now possible to prevent most races, which this patch attempts. Before starting the remount read-only, iterate through all mounts belonging to the superblock and if none of them have any pending writes, set sb->s_readonly_remount. This indicates that remount is in progress and no further write requests are allowed. If the remount succeeds set MS_RDONLY and reset s_readonly_remount. If the remounting is unsuccessful just reset s_readonly_remount. This can result in transient EROFS errors, despite the fact the remount failed. Unfortunately hodling off writes is difficult as remount itself may touch the filesystem (e.g. through load_nls()) which would deadlock. A later patch deals with delayed writes due to nlink going to zero. Signed-off-by: Miklos Szeredi Tested-by: Toshiyuki Okajima Signed-off-by: Al Viro

Merge branches 'vfsmount-guts', 'umode_t' and 'partitions' into Z

2012-01-07T04:15:54Z

vfs: spread struct mount - __lookup_mnt() result

2012-01-04T03:56:58Z

switch __lookup_mnt() to returning struct mount *; callers adjusted. Signed-off-by: Al Viro

switch open and mkdir syscalls to umode_t

2012-01-04T03:55:19Z

Signed-off-by: Al Viro

vfs: new helper - vfs_ustat()

2012-01-04T03:53:07Z

... and bury user_get_super()/statfs_by_dentry() - they are purely internal now. Signed-off-by: Al Viro

trim fs/internal.h

2012-01-04T03:52:35Z

some stuff in there can actually become static; some belongs to pnode.h as it's a private interface between namespace.c and pnode.c... Signed-off-by: Al Viro

superblock: move pin_sb_for_writeback() to fs/super.c

2011-07-20T05:44:38Z

The per-sb shrinker has the same requirement as the writeback threads of ensuring that the superblock is usable and pinned for the time it takes to run the work. Both need to take a passive reference to the sb, take a read lock on the s_umount lock and then only continue if an unmount is not in progress. pin_sb_for_writeback() does this exactly, so move it to fs/super.c and rename it to grab_super_passive() and exporting it via fs/internal.h for all the VFS code to be able to use. Signed-off-by: Dave Chinner Signed-off-by: Al Viro

Make ->d_sb assign-once and always non-NULL

2011-07-20T05:44:17Z

New helper (non-exported, fs/internal.h-only): __d_alloc(sb, name). Allocates dentry, sets its ->d_sb to given superblock and sets ->d_op accordingly. Old d_alloc(NULL, name) callers are converted to that (all of them know what superblock they want). d_alloc() itself is left only for parent != NULl case; uses __d_alloc(), inserts result into the list of parent's children. Note that now ->d_sb is assign-once and never NULL *and* ->d_parent is never NULL either. Signed-off-by: Al Viro

fs: move i_wb_list out from under inode_lock

2011-03-25T01:17:51Z

Protect the inode writeback list with a new global lock inode_wb_list_lock and use it to protect the list manipulations and traversals. This lock replaces the inode_lock as the inodes on the list can be validity checked while holding the inode->i_lock and hence the inode_lock is no longer needed to protect the list. Signed-off-by: Dave Chinner Signed-off-by: Al Viro

fs: move i_sb_list out from under inode_lock

2011-03-25T01:16:32Z

Protect the per-sb inode list with a new global lock inode_sb_list_lock and use it to protect the list manipulations and traversals. This lock replaces the inode_lock as the inodes on the list can be validity checked while holding the inode->i_lock and hence the inode_lock is no longer needed to protect the list. Signed-off-by: Dave Chinner Signed-off-by: Al Viro