From: Trond Myklebust <trondmy@hammerspace.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 bugfixes for Linux 5.9
Date: Wed, 9 Sep 2020 17:52:01 +0000 [thread overview]
Message-ID: <f96776cef2b96ae904dd7f0c58a96c964cb9a950.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:
Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.9-2
for you to fetch changes up to 8c6b6c793ed32b8f9770ebcdf1ba99af423c303b:
SUNRPC: stop printk reading past end of string (2020-09-05 10:39:41 -0400)
----------------------------------------------------------------
NFS client bugfixes for Linux 5.9
Highlights include:
Bugfixes:
- Fix an NFS/RDMA resource leak
- Fix the error handling during delegation recall
- NFSv4.0 needs to return the delegation on a zero-stateid SETATTR
- Stop printk reading past end of string
----------------------------------------------------------------
Chuck Lever (2):
xprtrdma: Release in-flight MRs on disconnect
NFS: Zero-stateid SETATTR should first return delegation
J. Bruce Fields (1):
SUNRPC: stop printk reading past end of string
Olga Kornievskaia (1):
NFSv4.1 handle ERR_DELAY error reclaiming locking state on delegation recall
Trond Myklebust (1):
Merge tag 'nfs-rdma-for-5.9-1' of git://git.linux-nfs.org/projects/anna/linux-nfs
fs/nfs/nfs4proc.c | 11 +++++++++--
net/sunrpc/rpcb_clnt.c | 4 ++--
net/sunrpc/xprtrdma/verbs.c | 2 ++
3 files changed, 13 insertions(+), 4 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2020-09-09 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 17:52 Trond Myklebust [this message]
2020-09-10 0:27 ` 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=f96776cef2b96ae904dd7f0c58a96c964cb9a950.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®