From: "Schumaker, Anna" <Anna.Schumaker@netapp.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.linux.org" <linux-nfs@vger.linux.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for 5.0-rc3
Date: Fri, 18 Jan 2019 21:21:08 +0000 [thread overview]
Message-ID: <a8ab9ed89d15439b0d4332f2170a6aa5bf9bfb46.camel@netapp.com> (raw)
Hi Linus,
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.0-2
for you to fetch changes up to deaa5c96c2f7e8b934088a1e70a0fe8797bd1149:
SUNRPC: Address Kerberos performance/behavior regression (2019-01-15 15:36:41
-0500)
----------------------------------------------------------------
These are mostly fixes for SUNRPC bugs, with a single v4.2 copy_file_range() fix
mixed in.
Stable bugfixes:
- Fix TCP receive code on archs with flush_dcache_page()
Other bugfixes:
- Fix error code in rpcrdma_buffer_create()
- Fix a double free in rpcrdma_send_ctxs_create()
- Fix kernel BUG at kernel/cred.c:825
- Fix unnecessary retry in nfs42_proc_copy_file_range()
- Ensure rq_bytes_sent is reset before request transmission
- Ensure we respect the RPCSEC_GSS sequence number limit
- Address Kerberos performance/behavior regression
Thanks,
Anna
----------------------------------------------------------------
Chuck Lever (1):
SUNRPC: Address Kerberos performance/behavior regression
Dan Carpenter (2):
xprtrdma: Fix error code in rpcrdma_buffer_create()
xprtrdma: Double free in rpcrdma_sendctxs_create()
Olga Kornievskaia (1):
NFSv4.2 fix unnecessary retry in nfs4_copy_file_range
Santosh kumar pradhan (1):
sunrpc: kernel BUG at kernel/cred.c:825!
Trond Myklebust (3):
SUNRPC: Fix TCP receive code on archs with flush_dcache_page()
SUNRPC: Ensure rq_bytes_sent is reset before request transmission
SUNRPC: Ensure we respect the RPCSEC_GSS sequence number limit
fs/nfs/nfs4file.c | 8 +-------
net/sunrpc/auth.c | 3 +++
net/sunrpc/auth_gss/auth_gss.c | 12 +++++++++---
net/sunrpc/clnt.c | 20 ++++++++++++--------
net/sunrpc/xprt.c | 3 ++-
net/sunrpc/xprtrdma/verbs.c | 10 ++++------
net/sunrpc/xprtsock.c | 22 ++++++++++++++++++++++
7 files changed, 53 insertions(+), 25 deletions(-)
next reply other threads:[~2019-01-18 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 21:21 Schumaker, Anna [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-18 21:20 [GIT PULL] Please pull NFS client bugfixes for 5.0-rc3 Schumaker, Anna
2019-01-19 22:00 ` 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=a8ab9ed89d15439b0d4332f2170a6aa5bf9bfb46.camel@netapp.com \
--to=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.linux.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).