linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Schumaker, Anna" <Anna.Schumaker@netapp.com>
To: "torvalds@linux-foundation.org" <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>
Subject: [GIT PULL] Please pull NFS Client Bugfixes for Linux 5.4-rc6
Date: Fri, 1 Nov 2019 20:53:30 +0000	[thread overview]
Message-ID: <2c39701ab77496cb78b4955aad532a2f18427465.camel@netapp.com> (raw)

Hi Linus,

The following changes since commit 9e5eefba3d098d66defa1ce59a34a41a96f49771:

  Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost (2019-10-28
12:47:22 +0100)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.4-3

for you to fetch changes up to 79cc55422ce99be5964bde208ba8557174720893:

  NFS: Fix an RCU lock leak in nfs4_refresh_delegation_stateid() (2019-11-01 11:03:56 -0400)

----------------------------------------------------------------
This patch set contains two delegation fixes (with the RCU lock leak fix marked
for stable), and three patches to fix destroying the the sunrpc back channel.

Thanks,
Anna

----------------------------------------------------------------

Trond Myklebust (5):
      SUNRPC: The TCP back channel mustn't disappear while requests are outstanding
      SUNRPC: The RDMA back channel mustn't disappear while requests are outstanding
      SUNRPC: Destroy the back channel when we destroy the host transport
      NFSv4: Don't allow a cached open with a revoked delegation
      NFS: Fix an RCU lock leak in nfs4_refresh_delegation_stateid()

 fs/nfs/delegation.c               | 12 +++++++++++-
 fs/nfs/delegation.h               |  1 +
 fs/nfs/nfs4proc.c                 |  7 ++-----
 include/linux/sunrpc/bc_xprt.h    |  5 +++++
 net/sunrpc/backchannel_rqst.c     |  7 ++++---
 net/sunrpc/xprt.c                 |  5 +++++
 net/sunrpc/xprtrdma/backchannel.c |  2 ++
 7 files changed, 30 insertions(+), 9 deletions(-)

             reply	other threads:[~2019-11-01 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01 20:53 Schumaker, Anna [this message]
2019-11-02  1:10 ` [GIT PULL] Please pull NFS Client Bugfixes for Linux 5.4-rc6 pr-tracker-bot

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=2c39701ab77496cb78b4955aad532a2f18427465.camel@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;
as well as URLs for NNTP newsgroup(s).