From: "Schumaker, Anna" <Anna.Schumaker@netapp.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS Client fixes for 5.6-rc6
Date: Fri, 13 Mar 2020 21:23:52 +0000 [thread overview]
Message-ID: <301a18ca0151b97f54ff6f67b4d32afed696459b.camel@netapp.com> (raw)
Hi Linus,
The following changes since commit 5d63944f8206a80636ae8cb4b9107d3b49f43d37:
NFSv4: Ensure the delegation cred is pinned when we call delegreturn (2020-02-
13 16:23:02 -0500)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.6-3
for you to fetch changes up to 55dee1bc0d72877b99805e42e0205087e98b9edd:
nfs: add minor version to nfs_server_key for fscache (2020-02-25 13:53:24
-0500)
----------------------------------------------------------------
These are mostly fscontext fixes, but there is also one that fixes collisions
seen in fscache.
Thanks,
Anna
----------------------------------------------------------------
Scott Mayhew (4):
NFS: Ensure the fs_context has the correct fs_type before mounting
NFS: Don't hard-code the fs_type when submounting
NFS: Fix leak of ctx->nfs_server.hostname
nfs: add minor version to nfs_server_key for fscache
fs/nfs/client.c | 1 +
fs/nfs/fs_context.c | 9 +++++++++
fs/nfs/fscache.c | 2 ++
fs/nfs/namespace.c | 2 +-
fs/nfs/nfs4client.c | 1 -
5 files changed, 13 insertions(+), 2 deletions(-)
next reply other threads:[~2020-03-13 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 21:23 Schumaker, Anna [this message]
2020-03-13 22:30 ` [GIT PULL] Please pull NFS Client fixes for 5.6-rc6 pr-tracker-bot
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=301a18ca0151b97f54ff6f67b4d32afed696459b.camel@netapp.com \
--to=anna.schumaker@netapp.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).