public inbox for linux-nfs@vger.kernel.org
 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] A few more NFS client bugfixes for 5.2
Date: Fri, 21 Jun 2019 19:36:06 +0000	[thread overview]
Message-ID: <5fd7ed91090e8c12df4968440d74f88f86dba612.camel@netapp.com> (raw)

Hi Linus,

The following changes since commit
9e0babf2c06c73cda2c0cd37a1653d823adb40ec:

  Linux 5.2-rc5 (2019-06-16 08:49:45 -1000)

are available in the Git repository at:

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

for you to fetch changes up to
19d55046cd824baab53534ba7e7f99945c6fdcb1:

  SUNRPC: Fix a credential refcount leak (2019-06-21 14:45:09 -0400)

----------------------------------------------------------------
These are mostly refcounting issues that people have found recently.   
The revert fixes a suspend recovery performance issue.

Thanks,
Anna
----------------------------------------------------------------
Anna
Schumaker (1):
      Revert "SUNRPC: Declare RPC timers as TIMER_DEFERRABLE"

Benjamin Coddington (1):
      NFS4: Only set creation opendata if O_CREAT

Lin Yi (1):
      net :sunrpc :clnt :Fix xps refcount imbalance on the error path

Trond Myklebust (1):
      SUNRPC: Fix a credential refcount leak

 fs/nfs/nfs4proc.c  | 20 +++++++++++---------
 net/sunrpc/clnt.c  |  2 +-
 net/sunrpc/sched.c |  4 +---
 net/sunrpc/xprt.c  |  4 +---
 4 files changed, 14 insertions(+), 16 deletions(-)

                 reply	other threads:[~2019-06-21 19:36 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=5fd7ed91090e8c12df4968440d74f88f86dba612.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