From: Trond Myklebust <trondmy@hammerspace.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 changes
Date: Fri, 8 Apr 2022 17:30:43 +0000 [thread overview]
Message-ID: <9c98642c7b088e4e5a628b1aa144df8eafa25cfa.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit 7c9d845f0612e5bcd23456a2ec43be8ac43458f1:
NFSv4/pNFS: Fix another issue with a list iterator pointing to the head (2022-03-28 08:36:34 -0400)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.18-2
for you to fetch changes up to ff053dbbaffec45c85e5bfe43306d26694a6433f:
SUNRPC: Move the call to xprt_send_pagedata() out of xprt_sock_sendmsg() (2022-04-07 16:20:01 -0400)
----------------------------------------------------------------
NFS client bugfixes for Linux 5.18
Highlights include:
Stable fixes:
- SUNRPC: Ensure we flush any closed sockets before xs_xprt_free()
Bugfixes:
- Fix an Oopsable condition due to SLAB_ACCOUNT setting in the NFSv4.2
xattr code.
- Fix for open() using an file open mode of '3' in NFSv4
- Replace readdir's use of xxhash() with hash_64()
- Several patches to handle malloc() failure in SUNRPC
----------------------------------------------------------------
ChenXiaoSong (2):
Revert "NFSv4: Handle the special Linux file open access mode"
NFSv4: fix open failure with O_ACCMODE flag
Muchun Song (1):
NFSv4.2: Fix missing removal of SLAB_ACCOUNT on kmem_cache allocation
NeilBrown (1):
SUNRPC: handle malloc failure in ->request_prepare
Trond Myklebust (9):
NFS: Replace readdir's use of xxhash() with hash_64()
SUNRPC: Ensure we flush any closed sockets before xs_xprt_free()
SUNRPC: Handle ENOMEM in call_transmit_status()
SUNRPC: Handle low memory situations in call_status()
NFSv4/pnfs: Handle RPC allocation errors in nfs4_proc_layoutget
NFS: Ensure rpc_run_task() cannot fail in nfs_async_rename()
SUNRPC: Handle allocation failure in rpc_new_task()
SUNRPC: svc_tcp_sendmsg() should handle errors from xdr_alloc_bvec()
SUNRPC: Move the call to xprt_send_pagedata() out of xprt_sock_sendmsg()
fs/file_table.c | 1 +
fs/nfs/Kconfig | 4 ----
fs/nfs/dir.c | 19 +++----------------
fs/nfs/inode.c | 1 -
fs/nfs/internal.h | 10 ++++++++++
fs/nfs/nfs42xattr.c | 2 +-
fs/nfs/nfs4file.c | 6 ++++--
fs/nfs/nfs4proc.c | 2 ++
fs/nfs/unlink.c | 1 +
include/linux/nfs_xdr.h | 1 +
include/linux/sunrpc/xprt.h | 5 ++---
include/trace/events/sunrpc.h | 1 -
net/sunrpc/clnt.c | 20 +++++++++++++++++---
net/sunrpc/sched.c | 5 +++++
net/sunrpc/socklib.c | 6 ------
net/sunrpc/svcsock.c | 13 +++++++++----
net/sunrpc/xprt.c | 30 ++++++++++++++++--------------
net/sunrpc/xprtsock.c | 33 +++++++++++++++++++++++++++------
18 files changed, 99 insertions(+), 61 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2022-04-08 17:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 17:30 Trond Myklebust [this message]
2022-04-08 17:46 ` [GIT PULL] Please pull NFS client changes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2018-12-06 21:55 Trond Myklebust
2018-12-07 18:35 ` pr-tracker-bot
2018-11-25 3:04 Trond Myklebust
2018-11-25 17:45 ` pr-tracker-bot
2018-01-30 14:39 Trond Myklebust
2017-10-09 17:35 Trond Myklebust
2016-01-14 21:09 Trond Myklebust
2015-09-07 20:59 Trond Myklebust
2015-09-08 1:59 ` Stephen Rothwell
2015-09-08 6:01 ` Christoph Hellwig
2015-09-11 16:27 ` Christoph Hellwig
2015-09-11 17:06 ` Trond Myklebust
2014-12-08 3:09 Trond Myklebust
2014-10-06 13:03 Trond Myklebust
2014-07-19 20:07 Trond Myklebust
2014-01-27 16:49 Trond Myklebust
2011-10-25 12:25 Trond Myklebust
2011-07-27 18:40 [GIT PULL] Please pull nfs " Trond Myklebust
2011-03-17 17:19 [GIT PULL] Please pull NFS " Trond Myklebust
2011-01-11 23:08 Trond Myklebust
2010-08-06 18:26 Trond Myklebust
2010-05-17 22:28 Trond Myklebust
2010-05-18 8:59 ` Lukas Hejtmanek
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=9c98642c7b088e4e5a628b1aa144df8eafa25cfa.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).