From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: [GIT PULL] Please pull NFS client bugfixes for 4.7
Date: Wed, 29 Jun 2016 17:04:25 -0400 [thread overview]
Message-ID: <aae88d1b-ce34-d0da-b971-a212a199bec9@Netapp.com> (raw)
Hi Linus,
The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e:
Linux 4.7-rc4 (2016-06-19 21:30:02 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.7-2
for you to fetch changes up to e547f2628327fec6afd2e03b46f113f614cca05b:
NFS: Fix another OPEN_DOWNGRADE bug (2016-06-28 16:55:34 -0400)
Thanks,
Anna
----------------------------------------------------------------
Al Viro (1):
make nfs_atomic_open() call d_drop() on all ->open_context() errors.
Oleg Drokin (1):
nfs4: Fix potential use after free of state in nfs4_do_reclaim.
Trond Myklebust (11):
NFSv4.1/pnfs: Ensure we handle delegation errors in nfs4_proc_layoutget()
NFSv4.1/pnfs: Layout stateids start out as being invalid
NFSv4.1/pnfs: Add sparse lock annotations for pnfs_find_alloc_layout
NFS/pnfs: handle bad delegation stateids in nfs4_layoutget_handle_exception
NFS: Fix up O_DIRECT results
NFS: Fix a double page unlock
NFSv4.1/pnfs: Mark the layout stateid invalid when all segments are removed
NFS: Don't let readdirplus revalidate an inode that was marked as stale
NFS: Fix potential race in nfs_fhget()
NFS: Fix an unused variable warning
NFS: Fix another OPEN_DOWNGRADE bug
Weston Andros Adamson (1):
pnfs_nfs: fix _cancel_empty_pagelist
fs/nfs/dir.c | 11 +++++++----
fs/nfs/direct.c | 10 +++++++---
fs/nfs/inode.c | 1 +
fs/nfs/nfs4proc.c | 18 ++++++++++--------
fs/nfs/nfs4state.c | 2 +-
fs/nfs/pnfs.c | 10 +++++++---
fs/nfs/pnfs_nfs.c | 12 ++++++++++--
fs/nfs/read.c | 4 ++--
8 files changed, 45 insertions(+), 23 deletions(-)
reply other threads:[~2016-06-29 21:04 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=aae88d1b-ce34-d0da-b971-a212a199bec9@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@primarydata.com \
/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
Powered by JetHome