From: Anna Schumaker <Anna.Schumaker@Netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull a few more NFS client fixes for 4.13
Date: Fri, 11 Aug 2017 16:40:46 -0400 [thread overview]
Message-ID: <4a7ac662-682c-85f4-d434-8a03929d407f@Netapp.com> (raw)
Hi Linus,
The following changes since commit d9cb73300ac0001832c048a489c592263fc28193:
NFSv4: Fix double frees in nfs4_test_session_trunk() (2017-08-02 09:45:55 -0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.13-5
for you to fetch changes up to 8a9d6e964d318533ba3d2901ce153ba317c99a89:
pnfs/blocklayout: require 64-bit sector_t (2017-08-11 14:10:13 -0400)
----------------------------------------------------------------
A few more bugfixes from me for rc5. Dros has a stable fix for flexfiles to prevent
leaking the nfs4_ff_ds_version arrays when freeing a layout, Trond fixed a potential
recovery loop situation with the TEST_STATEID operation, and Christoph fixed up the
pNFS blocklayout Kconfig options to prevent unsafe use with kernels that don't have
large block device support.
Have a good weekend!
Anna
----------------------------------------------------------------
Christoph Hellwig (1):
pnfs/blocklayout: require 64-bit sector_t
Trond Myklebust (1):
NFSv4: Ignore NFS4ERR_OLD_STATEID in nfs41_check_open_stateid()
Weston Andros Adamson (1):
nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
fs/nfs/Kconfig | 1 +
fs/nfs/flexfilelayout/flexfilelayoutdev.c | 1 +
fs/nfs/nfs4proc.c | 3 +--
3 files changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2017-08-11 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 20:40 Anna Schumaker [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-28 20:37 Anna Schumaker
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=4a7ac662-682c-85f4-d434-8a03929d407f@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®