From: Jeff Layton <jlayton@primarydata.com>
To: trond.myklebust@primarydata.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/3] nfsd: fix v4.0 GSSAPI callback channel auth failures
Date: Sat, 21 Jun 2014 20:52:14 -0400 [thread overview]
Message-ID: <1403398337-4174-1-git-send-email-jlayton@primarydata.com> (raw)
This is a respin of the kernel patchset that I sent back in early April
to fix the client's GSSAPI authentication in the v4.0 callback channel.
The userland piece of this has already been merged into nfs-utils.
The only real change here is to move the "stringification" of the
acceptor name out of the rpc_done callback and into the synchronous
caller. As Trond pointed out, we can't do that in rpciod callbacks as it
could recurse into writeback.
The callback now just takes a reference to the rpccred and stores a
pointer to it in the nfs4_setclientid struct. If that's non-NULL after
the call returns, we do the stringification there and then put the cred.
Jeff Layton (3):
auth_gss: fetch the acceptor name out of the downcall
sunrpc: add a new "stringify_acceptor" rpc_credop
nfs4: copy acceptor name from context to nfs_client
fs/nfs/callback.c | 12 ++++++
fs/nfs/client.c | 1 +
fs/nfs/nfs4proc.c | 33 ++++++++++++++++-
include/linux/nfs_fs_sb.h | 1 +
include/linux/nfs_xdr.h | 1 +
include/linux/sunrpc/auth.h | 2 +
include/linux/sunrpc/auth_gss.h | 1 +
net/sunrpc/auth.c | 9 +++++
net/sunrpc/auth_gss/auth_gss.c | 82 +++++++++++++++++++++++++++++------------
9 files changed, 118 insertions(+), 24 deletions(-)
--
1.9.3
next reply other threads:[~2014-06-22 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 0:52 Jeff Layton [this message]
2014-06-22 0:52 ` [PATCH v2 1/3] auth_gss: fetch the acceptor name out of the downcall Jeff Layton
2014-06-22 0:52 ` [PATCH v2 2/3] sunrpc: add a new "stringify_acceptor" rpc_credop Jeff Layton
2014-06-22 0:52 ` [PATCH v2 3/3] nfs4: copy acceptor name from context to nfs_client Jeff Layton
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=1403398337-4174-1-git-send-email-jlayton@primarydata.com \
--to=jlayton@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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