From: bjschuma@netapp.com
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, steved@redhat.com,
Bryan Schumaker <bjschuma@netapp.com>
Subject: [PATCH v4 0/9] Fix SECINFO procedure
Date: Thu, 26 Apr 2012 16:56:03 -0400 [thread overview]
Message-ID: <1335473772-4401-1-git-send-email-bjschuma@netapp.com> (raw)
From: Bryan Schumaker <bjschuma@netapp.com>
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 4:
- Reorder patches to fix the bug first and then clean up files
Changes in version 3:
- Don't define decode_secinfo_no_name() if CONFIG_NFS_V4_1 isn't set
- Move around function declerations in header files
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 (9):
NFS: Fix SECINFO_NO_NAME
NFS: Handle exceptions coming out of nfs4_proc_fs_locations()
NFS: Do secinfo as part of lookup
NFS: Fix following referral mount points with different security
NFS: Honor the authflavor set in the clone mount data
NFS: Remove unused function nfs_lookup_with_sec()
NFS: Remove secinfo knowledge out of the generic client
NFS: Create a submount rpc_op
NFS: Remove extra rpc_clnt argument to proc_lookup
fs/nfs/client.c | 5 +-
fs/nfs/dir.c | 6 +-
fs/nfs/internal.h | 22 ++------
fs/nfs/namespace.c | 140 ++++++-----------------------------------------
fs/nfs/nfs3proc.c | 3 +-
fs/nfs/nfs4_fs.h | 13 ++++-
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(+), 184 deletions(-)
--
1.7.10
next reply other threads:[~2012-04-26 20:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 20:56 bjschuma [this message]
2012-04-26 20:56 ` [PATCH v4 1/9] NFS: Fix SECINFO_NO_NAME bjschuma
2012-04-26 20:56 ` [PATCH v4 2/9] NFS: Handle exceptions coming out of nfs4_proc_fs_locations() bjschuma
2012-04-26 20:56 ` [PATCH v4 3/9] NFS: Do secinfo as part of lookup bjschuma
2012-04-26 20:56 ` [PATCH v4 4/9] NFS: Fix following referral mount points with different security bjschuma
2012-04-26 20:56 ` [PATCH v4 5/9] NFS: Honor the authflavor set in the clone mount data bjschuma
2012-04-26 20:56 ` [PATCH v4 6/9] NFS: Remove unused function nfs_lookup_with_sec() bjschuma
2012-04-27 16:06 ` Myklebust, Trond
2012-04-27 16:12 ` Bryan Schumaker
2012-04-26 20:56 ` [PATCH v4 7/9] NFS: Remove secinfo knowledge out of the generic client bjschuma
2012-04-26 20:56 ` [PATCH v4 8/9] NFS: Create a submount rpc_op bjschuma
2012-04-26 20:56 ` [PATCH v4 9/9] NFS: Remove extra rpc_clnt argument to proc_lookup bjschuma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1335473772-4401-1-git-send-email-bjschuma@netapp.com \
--to=bjschuma@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox