From: Anna Schumaker <Anna.Schumaker@Netapp.com>
To: <torvalds@linux-foundation.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for 4.11
Date: Fri, 17 Mar 2017 16:21:11 -0400 [thread overview]
Message-ID: <2142a302-6319-a6e4-2c4e-46f37e8ac084@Netapp.com> (raw)
Hi Linus,
The following changes since commit ed92d8c137b7794c2c2aa14479298b9885967607:
NFSv4: fix getacl ERANGE for some ACL buffer sizes (2017-02-23 17:23:35 -0500)
are available in the git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.11-2
for you to fetch changes up to da066f3f039eba3e72e97b2ccad0dd8b45ba84bd:
pNFS/flexfiles: never nfs4_mark_deviceid_unavailable (2017-03-17 16:07:17 -0400)
----------------------------------------------------------------
We have a handful of stable fixes to fix kernel warnings and other bugs that have been
around for a while. We've also found a few other reference counting bugs and memory leaks since the initial 4.11 pull.
Stable Bugfixes:
- Fix decrementing nrequests in NFS v4.2 COPY to fix kernel warnings
- Prevent a double free in async nfs4_exchange_id()
- Squelch a kbuild sparse complaint for xprtrdma
Other Bugfixes:
- Fix a typo (NFS_ATTR_FATTR_GROUP_NAME) that causes a memory leak
- Fix a reference leak that causes kernel warnings
- Make nfs4_cb_sv_ops static to fix a sparse warning
- Respect a server's max size in CREATE_SESSION
- Handle errors from nfs4_pnfs_ds_connect
- Flexfiles layout shouldn't mark devices as unavailable
Thanks,
Anna
----------------------------------------------------------------
Chuck Lever (1):
xprtrdma: Squelch kbuild sparse complaint
Jason Yan (1):
nfs: make nfs4_cb_sv_ops static
Kinglong Mee (3):
nfs4: fix a typo of NFS_ATTR_FATTR_GROUP_NAME
NFSv4: fix a reference leak caused WARNING messages
NFS: fix the fault nrequests decreasing for nfs_inode COPY
Olga Kornievskaia (2):
NFS prevent double free in async nfs4_exchange_id
NFSv4.1 respect server's max size in CREATE_SESSION
Weston Andros Adamson (2):
pNFS: return status from nfs4_pnfs_ds_connect
pNFS/flexfiles: never nfs4_mark_deviceid_unavailable
fs/nfs/callback.c | 4 ++--
fs/nfs/client.c | 25 ++++++++++++++++++++++++-
fs/nfs/filelayout/filelayoutdev.c | 8 +++++++-
fs/nfs/flexfilelayout/flexfilelayout.h | 14 +++++++++++++-
fs/nfs/flexfilelayout/flexfilelayoutdev.c | 5 +++--
fs/nfs/internal.h | 2 ++
fs/nfs/nfs4client.c | 4 ++--
fs/nfs/nfs4proc.c | 11 ++++-------
fs/nfs/nfs4xdr.c | 2 +-
fs/nfs/pnfs.h | 2 +-
fs/nfs/pnfs_nfs.c | 31 +++++++++++++++++++++++++------
fs/nfs/write.c | 6 ++++--
net/sunrpc/xprtrdma/verbs.c | 3 ++-
13 files changed, 90 insertions(+), 27 deletions(-)
reply other threads:[~2017-03-17 20:21 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=2142a302-6319-a6e4-2c4e-46f37e8ac084@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®