From: Anna Schumaker <Anna.Schumaker@Netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Linux NFS Mailing List" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for 4.15
Date: Fri, 15 Dec 2017 16:43:49 -0500 [thread overview]
Message-ID: <a0189ebe-a038-99ec-a388-59572b1549cd@Netapp.com> (raw)
Hi Linus,
The following changes since commit eb5b46faa693470681ec7c28cc2436edd1571198:
SUNRPC: Handle ENETDOWN errors (2017-11-30 11:52:52 -0500)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.15-3
for you to fetch changes up to 90d91b0cd371193d9dbfa9beacab8ab9a4cb75e0:
SUNRPC: Fix a race in the receive code path (2017-12-15 14:31:56 -0500)
----------------------------------------------------------------
This pull request has two stable bugfixes, one to fix a BUG_ON() when nfs_commit_inode() is called with no outstanding commit requests and another to fix a race in the SUNRPC receive codepath.
Additionally, there are also fixes for an NFS client deadlock and an xprtrdma performance regression.
Cheers,
Anna
----------------------------------------------------------------
Chuck Lever (1):
xprtrdma: Spread reply processing over more CPUs
Scott Mayhew (2):
nfs: fix a deadlock in nfs client initialization
nfs: don't wait on commit in nfs_commit_inode() if there were no commit requests
Trond Myklebust (1):
SUNRPC: Fix a race in the receive code path
fs/nfs/client.c | 11 +++++++++++
fs/nfs/nfs4client.c | 17 +++++++++++++----
fs/nfs/write.c | 2 ++
net/sunrpc/xprt.c | 28 +++++++++++++++++++---------
net/sunrpc/xprtrdma/rpc_rdma.c | 6 +-----
net/sunrpc/xprtrdma/transport.c | 2 ++
net/sunrpc/xprtrdma/verbs.c | 2 +-
net/sunrpc/xprtrdma/xprt_rdma.h | 1 +
8 files changed, 50 insertions(+), 19 deletions(-)
reply other threads:[~2017-12-15 21:53 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=a0189ebe-a038-99ec-a388-59572b1549cd@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
all inboxes | Powered by JetHome®