From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [GIT PULL] nfsd changes for 4.19
Date: Thu, 23 Aug 2018 11:29:20 -0400 [thread overview]
Message-ID: <20180823152920.GE32415@fieldses.org> (raw)
In-Reply-To: <20180823125810.GC32415@fieldses.org>
Apologies, I messed up my pull request. The result was just a few
commits mentioned in the tag description but missing from the tip of the
branch, and I thought simplest was to make a new tag and a new pull
request with the additional commits, I hope that works OK. Thanks to
Chuck for noticing the problem quickly. Please pull:
git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.19-1
--b.
----------------------------------------------------------------
A mistake on my part caused me to tag my branch 6 commits too early,
missing Chuck's fixes for the problem with callbacks over GSS from
multi-homed servers, and a smaller fix from Laura Abbott.
----------------------------------------------------------------
Chuck Lever (5):
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
sunrpc: Add comment defining gssd upcall API keywords
Laura Abbott (1):
sunrpc: Don't use stack buffer with scatterlist
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 | 37 ++++++++++++++++--
net/sunrpc/auth_gss/gss_krb5_crypto.c | 12 ++++--
net/sunrpc/auth_gss/gss_rpc_upcall.c | 70 ++++++++++++++++++++++-------------
7 files changed, 106 insertions(+), 64 deletions(-)
prev parent reply other threads:[~2018-08-23 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 12:58 [GIT PULL] nfsd changes for 4.19 J. Bruce Fields
2018-08-23 15:29 ` J. Bruce Fields [this message]
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=20180823152920.GE32415@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).