From: Trond Myklebust <trondmy@primarydata.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 client fixes
Date: Mon, 12 Sep 2016 19:28:24 +0000 [thread overview]
Message-ID: <1473708502.6434.1.camel@primarydata.com> (raw)
Hi Linus,
The following changes since commit 98b0f80c2396224bbbed81792b526e6c72ba9efa:
NFSv4.x: Fix a refcount leak in nfs_callback_up_net (2016-08-30 09:26:57 -0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.8-4
for you to fetch changes up to b519d408ea32040b1c7e10b155a3ee9a36660947:
NFSv4.1: Fix the CREATE_SESSION slot number accounting (2016-09-11 14:56:44 -0400)
Cheers
Trond
----------------------------------------------------------------
NFS client bugfixes for 4.8
Highlights include:
Stable patches:
- We must serialise LAYOUTGET and LAYOUTRETURN to ensure correct state
accounting
- Fix the CREATE_SESSION slot number
Bugfixes:
- sunrpc: fix a UDP memory accounting regression
- NFS: Fix an error reporting regression in nfs_file_write()
- pNFS: Fix further layout stateid issues
- RPC/rdma: Revert 3d4cf35bd4fa ("xprtrdma: Reply buffer exhaustion...")
- RPC/rdma: Fix receive buffer accounting
----------------------------------------------------------------
Chuck Lever (2):
xprtrdma: Revert 3d4cf35bd4fa ("xprtrdma: Reply buffer exhaustion...")
xprtrdma: Fix receive buffer accounting
Paolo Abeni (1):
sunrpc: fix UDP memory accounting
Trond Myklebust (6):
NFS: Fix error reporting in nfs_file_write()
pNFS: Ensure LAYOUTGET and LAYOUTRETURN are properly serialised
pNFS: Fix pnfs_set_layout_stateid() to clear NFS_LAYOUT_INVALID_STID
pNFS: Clear out all layout segments if the server unsets lrp->res.lrs_present
pNFS: Don't forget the layout stateid if there are outstanding LAYOUTGETs
NFSv4.1: Fix the CREATE_SESSION slot number accounting
fs/nfs/file.c | 5 ++++-
fs/nfs/nfs4proc.c | 21 ++++++++++++++-----
fs/nfs/pnfs.c | 42 +++++++++++++++++++++-----------------
net/sunrpc/xprtrdma/verbs.c | 45 +++++++++++++++++++++++++++++------------
net/sunrpc/xprtrdma/xprt_rdma.h | 1 +
net/sunrpc/xprtsock.c | 2 +-
6 files changed, 78 insertions(+), 38 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
next reply other threads:[~2016-09-12 19:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 19:28 Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-26 20:12 [GIT PULL] Please pull NFS client fixes Trond Myklebust
2019-03-26 22:25 ` pr-tracker-bot
2017-10-24 22:56 Trond Myklebust
2016-02-23 18:33 Trond Myklebust
2014-09-12 17:04 Trond Myklebust
2014-08-29 19:35 Trond Myklebust
2014-08-25 14:55 Trond Myklebust
2014-02-19 14:13 Trond Myklebust
2014-02-19 14:40 ` Trond Myklebust
2014-02-04 16:52 Trond Myklebust
2013-07-19 19:27 Myklebust, Trond
2013-04-10 15:59 Myklebust, Trond
2013-01-31 19:47 Myklebust, Trond
2012-08-22 15:41 Myklebust, Trond
2011-06-21 18:36 Trond Myklebust
2010-12-10 18:05 Trond Myklebust
2010-12-09 3:11 Trond Myklebust
2010-04-13 21:54 Trond Myklebust
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=1473708502.6434.1.camel@primarydata.com \
--to=trondmy@primarydata.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