From: Bryan Schumaker <bjschuma@xxxxxxxxxx> My initial SECINFO implementation was merged in 2.6.39, but accidentally got disabled in 3.0. These patches re-enable SECINFO as part of LOOKUP and push it down to the v4 layer, instead of existing as an rpc_op (I create a "submount" rpc_op instead, see patch 5). I also noticed that SECINFO_NO_NAME was never run with the current xdr decoding logic. Patch 6 fixes this problem. Changes in version 2: - Reorder the patches so I'm not doing cleanup in the beginning - Don't pre-clone an rpc_clnt for nfs_clone_server, instead fix passing an rpc_authflavor_t through the nfs_clone_mount data. Comments are appreciated! - Bryan Bryan Schumaker (8): NFS: Fix SECINFO_NO_NAME NFS: Handle exceptions coming out of nfs4_proc_fs_locations() NFS: Do secinfo as part of lookup NFS: Remove secinfo knowledge out of the generic client NFS: Create a submount rpc_op NFS: Fix following referral mount points with different security NFS: Honor the authflavor set in the clone mount data NFS: Remove extra rpc_clnt argument to proc_lookup fs/nfs/client.c | 5 +- fs/nfs/dir.c | 6 +- fs/nfs/internal.h | 20 +++---- fs/nfs/namespace.c | 140 ++++++----------------------------------------- fs/nfs/nfs3proc.c | 3 +- fs/nfs/nfs4_fs.h | 12 +++- fs/nfs/nfs4namespace.c | 107 +++++++++++++++++++++++++++++++++++- fs/nfs/nfs4proc.c | 111 +++++++++++++++++++++++++++++-------- fs/nfs/nfs4xdr.c | 26 ++++++--- fs/nfs/proc.c | 3 +- fs/nfs/super.c | 4 +- include/linux/nfs_xdr.h | 5 +- 12 files changed, 261 insertions(+), 181 deletions(-) -- 1.7.10 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
