linux-fsdevel.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-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: [GIT PULL] Two more Linux NFS client fixes
Date: Fri, 28 Jun 2019 21:08:31 +0000	[thread overview]
Message-ID: <89f621cf02c20863839561bfc0ef2ee36cbfe9ab.camel@netapp.com> (raw)

Hi Linus,

The following changes since commit
19d55046cd824baab53534ba7e7f99945c6fdcb1:

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

are available in the Git repository at:

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

for you to fetch changes up to
68f461593f76bd5f17e87cdd0bea28f4278c7268:

  NFS/flexfiles: Use the correct TCP timeout for flexfiles I/O (2019-
06-28 11:48:52 -0400)

----------------------------------------------------------------
These are both stable fixes. One to calculate the correct client
message length in the case of partial transmissions. And the other to
set the proper TCP timeout for flexfiles.

Thanks,
Anna
----------------------------------------------------------------
Trond Myklebust (2):
      SUNRPC: Fix up calculation of client message length
      NFS/flexfiles: Use the correct TCP timeout for flexfiles I/O

 fs/nfs/flexfilelayout/flexfilelayoutdev.c |  2 +-
 net/sunrpc/xprtsock.c                     | 16 ++++++++--------
 2 files changed, 9 insertions(+), 9 deletions(-)

                 reply	other threads:[~2019-06-28 21:08 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=89f621cf02c20863839561bfc0ef2ee36cbfe9ab.camel@netapp.com \
    --to=anna.schumaker@netapp.com \
    --cc=linux-fsdevel@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).