From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for 5.1
Date: Sat, 16 Mar 2019 18:33:33 +0000 [thread overview]
Message-ID: <3a30ab7dd854db06aca0a5f70b66e54cb9415c6e.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit 4d6c671ace569d4b0d3f8d92ab3aef18a5d166bc:
SUNRPC: Take the transport send lock before binding+connecting (2019-03-10 14:08:19 -0400)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.1-2
for you to fetch changes up to 5e3863fd597eba8c6679de805681631b1aad9bdb:
SUNRPC: Remove redundant check for the reply length in call_decode() (2019-03-15 13:11:36 -0400)
Cheers
Trond
----------------------------------------------------------------
NFS client bugfixes for Linux 5.1
Highlights include:
Bugfixes:
- Fix an Oops in SUNRPC back channel tracepoints
- Fix a SUNRPC client regression when handling oversized replies
- Fix the minimal size for SUNRPC reply buffer allocation
- rpc_decode_header() must always return a non-zero value on error
- Fix a typo in pnfs_update_layout()
Cleanups:
- Remove redundant check for the reply length in call_decode()
----------------------------------------------------------------
Olga Kornievskaia (1):
fix null pointer deref in tracepoints in back channel
Trond Myklebust (7):
pNFS: Fix a typo in pnfs_update_layout
SUNRPC: Fix a client regression when handling oversized replies
SUNRPC: Fix the minimal size for reply buffer allocation
SUNRPC: Use the ENOTCONN error on socket disconnect
SUNRPC: rpc_decode_header() must always return a non-zero value on error
SUNRPC: Handle the SYSTEM_ERR rpc error
SUNRPC: Remove redundant check for the reply length in call_decode()
fs/nfs/pnfs.c | 2 +-
include/trace/events/sunrpc.h | 6 ++++--
net/sunrpc/clnt.c | 32 ++++++++++++++------------------
net/sunrpc/xprt.c | 2 +-
net/sunrpc/xprtsock.c | 2 +-
5 files changed, 21 insertions(+), 23 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2019-03-16 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 18:33 Trond Myklebust [this message]
2019-03-16 21:25 ` [GIT PULL] Please pull NFS client bugfixes for 5.1 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=3a30ab7dd854db06aca0a5f70b66e54cb9415c6e.camel@hammerspace.com \
--to=trondmy@hammerspace.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).