From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS fixes for 4.20
Date: Thu, 15 Nov 2018 00:12:01 +0000 [thread overview]
Message-ID: <15f600c2e93b3c764a236168e47891c1f46fc2e5.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit ccda4af0f4b92f7b4c308d3acc262f4a7e3affad:
Linux 4.20-rc2 (2018-11-11 17:12:31 -0600)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.20-3
for you to fetch changes up to e39d8a186ed002854196668cb7562ffdfbc6d379:
NFSv4: Fix an Oops during delegation callbacks (2018-11-13 17:15:17 -0500)
Cheers,
Trond
----------------------------------------------------------------
NFS client bugfixes for Linux 4.20
Highlights include:
Stable fixes:
- Don't exit the NFSv4 state manager without clearing NFS4CLNT_MANAGER_RUNNING
Bugfixes:
- Fix an Oops when destroying the RPCSEC_GSS credential cache
- Fix an Oops during delegation callbacks
- Ensure that the NFSv4 state manager exits the loop on SIGKILL
- Fix a bogus get/put in generic_key_to_expire()
----------------------------------------------------------------
Trond Myklebust (5):
NFSv4: Don't exit the state manager without clearing NFS4CLNT_MANAGER_RUNNING
NFSv4: Ensure that the state manager exits the loop on SIGKILL
SUNRPC: Fix a Oops when destroying the RPCSEC_GSS credential cache
SUNRPC: Fix a bogus get/put in generic_key_to_expire()
NFSv4: Fix an Oops during delegation callbacks
fs/nfs/callback_proc.c | 4 +--
fs/nfs/delegation.c | 11 ++++++--
fs/nfs/nfs4state.c | 10 ++++---
net/sunrpc/auth_generic.c | 8 +-----
net/sunrpc/auth_gss/auth_gss.c | 61 +++++++++++++++++++++++++++++-------------
5 files changed, 60 insertions(+), 34 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2018-11-15 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 0:12 Trond Myklebust [this message]
2018-11-15 17:30 ` 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=15f600c2e93b3c764a236168e47891c1f46fc2e5.camel@hammerspace.com \
--to=trondmy@hammerspace.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
all inboxes | Powered by JetHome®