The patch titled
NFS: Fix NFS mountpoint crossing
has been removed from the -mm tree. Its filename was
nfs-fix-nfs-mountpoint-crossing.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: NFS: Fix NFS mountpoint crossing
From: Trond Myklebust <trond.myklebust@xxxxxxxxxx>
The check that was added to nfs_xdev_get_sb() to work around broken
servers, works fine for NFSv2, but causes mountpoint crossing on NFSv3 to
always return ESTALE.
Signed-off-by: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/nfs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/nfs/super.c~nfs-fix-nfs-mountpoint-crossing fs/nfs/super.c
--- a/fs/nfs/super.c~nfs-fix-nfs-mountpoint-crossing
+++ a/fs/nfs/super.c
@@ -1499,7 +1499,7 @@ static int nfs_xdev_get_sb(struct file_s
error = PTR_ERR(mntroot);
goto error_splat_super;
}
- if (mntroot->d_inode->i_op != &nfs_dir_inode_operations) {
+ if (mntroot->d_inode->i_op != server->nfs_client->rpc_ops->dir_inode_ops) {
dput(mntroot);
error = -ESTALE;
goto error_splat_super;
_
Patches currently in -mm which might be from trond.myklebust@xxxxxxxxxx are
knfsd-change-mailing-list-for-nfsd-in-maintainers.patch
nfs-use-gfp_nofs-preloads-for-radix-tree-insertion.patch
git-nfsd.patch
nfs-fix-an-oops-in-nfs-unmount.patch
pagecache-zeroing-zero_user_segment-zero_user_segments-and-zero_user.patch
pagecache-zeroing-zero_user_segment-zero_user_segments-and-zero_user-fix.patch
pagecache-zeroing-zero_user_segment-zero_user_segments-and-zero_user-fix-2.patch
add-lock_page_killable.patch
kernel-add-mutex_lock_killable.patch
vfs-use-mutex_lock_killable-in-vfs_readdir.patch
create-file_drop_write_access-helper.patch
fix-up-new-filp-allocators.patch
embed-a-struct-path-into-struct-nameidata-instead-of-nd-dentrymnt-nfs4-fix.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
