From: Chuck Lever <chuck.lever@oracle.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org, simo@redhat.com
Subject: [PATCH v2 0/4] Use correct NFSv4.0 callback credential
Date: Thu, 16 Aug 2018 12:05:48 -0400 [thread overview]
Message-ID: <20180816160404.2230.55488.stgit@klimt.1015granger.net> (raw)
Hi Bruce-
This is the same series as I posted in May, merged up to v4.18. I
tested it again this morning. Can it be included in v4.19 ?
The previous thread claims Simo Ack'd these patches, but I can't
find the actual Acked-by. I've cc'd him on this repost in case he
has additional comments.
---
Chuck Lever (4):
sunrpc: Enable the kernel to specify the hostname part of service principals
sunrpc: Extract target name into svc_cred
nfsd: Use correct credential for NFSv4.0 callback with GSS
nfsd: Remove callback_cred
fs/nfsd/nfs4callback.c | 29 ++++----------
fs/nfsd/nfs4state.c | 17 +++-----
fs/nfsd/state.h | 2 -
include/linux/sunrpc/svcauth.h | 3 +
net/sunrpc/auth_gss/auth_gss.c | 20 ++++++++--
net/sunrpc/auth_gss/gss_rpc_upcall.c | 70 ++++++++++++++++++++++------------
6 files changed, 80 insertions(+), 61 deletions(-)
--
Chuck Lever
next reply other threads:[~2018-08-16 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 16:05 Chuck Lever [this message]
2018-08-16 16:05 ` [PATCH v2 1/4] sunrpc: Enable the kernel to specify the hostname part of service principals Chuck Lever
2018-08-16 16:27 ` Trond Myklebust
2018-08-16 16:39 ` Simo Sorce
2018-08-16 19:03 ` Chuck Lever
2018-08-17 4:54 ` Trond Myklebust
2018-08-17 13:43 ` Chuck Lever
2018-08-17 14:37 ` Trond Myklebust
2018-08-16 16:05 ` [PATCH v2 2/4] sunrpc: Extract target name into svc_cred Chuck Lever
2018-08-16 16:06 ` [PATCH v2 3/4] nfsd: Use correct credential for NFSv4.0 callback with GSS Chuck Lever
2018-08-16 16:06 ` [PATCH v2 4/4] nfsd: Remove callback_cred Chuck Lever
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=20180816160404.2230.55488.stgit@klimt.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=simo@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;
as well as URLs for NNTP newsgroup(s).