From: "Schumaker, Anna" <Anna.Schumaker@netapp.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.linux.org" <linux-nfs@vger.linux.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for 4.19
Date: Fri, 14 Sep 2018 20:32:22 +0000 [thread overview]
Message-ID: <9cf28df18cd2deba1b693df949e58efbcd299019.camel@netapp.com> (raw)
Hi Linus,
The following changes since commit 0af4c8be97a14d1df8a78b4993a09e8dff545a18:
pNFS: Remove unwanted optimisation of layoutget (2018-08-21 13:39:08 -0400)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.19-2
for you to fetch changes up to 9f0c5124f4a82503ee5d55c60b0b9c6afc3af68b:
NFS: Don't open code clearing of delegation state (2018-09-14 16:24:27 -0400)
----------------------------------------------------------------
These are a handful of fixes for problems that Trond found. Sorry that
patch #1 and #3 have the same name, a second issue was found after applying
the first patch.
Thanks,
Anna
----------------------------------------------------------------
Trond Myklebust (5):
NFSv4: Fix a tracepoint Oops in initiate_file_draining()
pNFS: Ensure we return the error if someone kills a waiting layoutget
NFSv4: Fix a tracepoint Oops in initiate_file_draining()
NFSv4.1 fix infinite loop on I/O.
NFS: Don't open code clearing of delegation state
fs/nfs/nfs4proc.c | 31 +++++++++++++++++++------------
fs/nfs/nfs4state.c | 2 ++
fs/nfs/nfs4trace.h | 4 ++--
fs/nfs/pnfs.c | 26 ++++++++++++++++----------
4 files changed, 39 insertions(+), 24 deletions(-)
reply other threads:[~2018-09-14 20:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9cf28df18cd2deba1b693df949e58efbcd299019.camel@netapp.com \
--to=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.linux.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).