kernel/git/stable/linux.git/fs/ncpfs/dir.c, branch linux-3.12.y

move d_rcu from overlapping d_child to overlapping d_alias

2015-01-29T14:45:16+00:00

commit 946e51f2bf37f1656916eb75bd0742ba33983c28 upstream. Signed-off-by: Al Viro Acked-by: Miklos Szeredi Signed-off-by: Jiri Slaby

Don't pass inode to ->d_hash() and ->d_compare()

2013-06-29T08:57:36+00:00

Instances either don't look at it at all (the majority of cases) or only want it to find the superblock (which can be had as dentry->d_sb). A few cases that want more are actually safe with dentry->d_inode - the only precaution needed is the check that it hadn't been replaced with NULL by rmdir() or by overwriting rename(), which case should be simply treated as cache miss. Signed-off-by: Linus Torvalds Signed-off-by: Al Viro

kill find_inode_number()

2013-06-29T08:57:20+00:00

the only remaining caller (in ncpfs) is guaranteed to return 0 - we only hit it if we'd just checked that there's no dentry with such name. Signed-off-by: Al Viro

ncpfs: don't bother with EBUSY on removal of busy directories

2013-06-29T08:57:16+00:00

Signed-off-by: Al Viro

[readdir] convert ncpfs

2013-06-29T08:56:57+00:00

Signed-off-by: Al Viro

ncpfs: fix rmdir returns Device or resource busy

2013-06-07T16:15:38+00:00

1d2ef5901483004d74947bbf78d5146c24038fe7 caused a regression in ncpfs such that directories could no longer be removed. This was because ncp_rmdir checked to see if a dentry could be unhashed before allowing it to be removed. Since 1d2ef5901483004d74947bbf78d5146c24038fe7 introduced a change that incremented dentry->d_count causing it to always be greater than 1 unhash would always fail. Thus causing the error path in ncp_rmdir to always be taken. Removing this error path is safe as unhashing is still accomplished by calls to dput from vfs_rmdir. Signed-off-by: Dave Chiluk Signed-off-by: Petr Vandrovec Signed-off-by: Al Viro

d_hash_and_lookup(): export, switch open-coded instances

2013-02-26T07:46:07+00:00

* calling conventions change - ERR_PTR() is returned on ->d_hash() errors; NULL is just for dcache miss now. * exported, open-coded instances in ncpfs and cifs converted. Signed-off-by: Al Viro

don't pass nameidata to ->create()

2012-07-14T12:34:47+00:00

boolean "does it have to be exclusive?" flag is passed instead; Local filesystem should just ignore it - the object is guaranteed not to be there yet. Signed-off-by: Al Viro

stop passing nameidata to ->lookup()

2012-07-14T12:34:32+00:00

Just the flags; only NFS cares even about that, but there are legitimate uses for such argument. And getting rid of that completely would require splitting ->lookup() into a couple of methods (at least), so let's leave that alone for now... Signed-off-by: Al Viro

stop passing nameidata * to ->d_revalidate()

2012-07-14T12:34:14+00:00

Just the lookup flags. Die, bastard, die... Signed-off-by: Al Viro