From: anna@kernel.org
To: torvalds@linux-foundation.org
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please Pull NFS Client Bugfixes for Linux v5.17-rc
Date: Tue, 8 Feb 2022 14:48:00 -0500 [thread overview]
Message-ID: <20220208194800.482704-1-anna@kernel.org> (raw)
Hi Linus,
The following changes since commit 26291c54e111ff6ba87a164d85d4a4e134b7315c:
Linux 5.17-rc2 (2022-01-30 15:37:07 +0200)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.17-2
for you to fetch changes up to b49ea673e119f59c71645e2f65b3ccad857c90ee:
SUNRPC: lock against ->sock changing during sysfs read (2022-02-08 09:14:26 -0500)
----------------------------------------------------------------
NFS Client Bugfixes for Linux 5.17-rc
- Stable Fixes:
- Fix initialization of nfs_client cl_flags
- Other Fixes:
- Fix performance issues with uncached readdir calls
- Fix potential pointer dereferences in rpcrdma_ep_create
- Fix nfs4_proc_get_locations() kernel-doc comment
- Fix locking during sunrpc sysfs reads
- Update my email address in the MAINTAINERS file to my new kernel.org email
Thanks,
Anna
----------------------------------------------------------------
Anna Schumaker (1):
MAINTAINERS: Update my email address
Dan Aloni (1):
xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create
NeilBrown (1):
SUNRPC: lock against ->sock changing during sysfs read
Trond Myklebust (2):
NFS: Avoid duplicate uncached readdir calls on eof
NFS: Fix initialisation of nfs_client cl_flags field
Yang Li (1):
NFS: Fix nfs4_proc_get_locations() kernel-doc comment
trondmy@kernel.org (2):
NFS: Don't overfill uncached readdir pages
NFS: Don't skip directory entries when doing uncached readdir
MAINTAINERS | 2 +-
fs/nfs/client.c | 2 +-
fs/nfs/dir.c | 24 ++++++++++++++++++------
fs/nfs/nfs4proc.c | 3 ++-
include/linux/nfs_fs.h | 1 +
net/sunrpc/sysfs.c | 5 ++++-
net/sunrpc/xprtrdma/verbs.c | 3 +++
net/sunrpc/xprtsock.c | 7 ++++++-
8 files changed, 36 insertions(+), 11 deletions(-)
next reply other threads:[~2022-02-08 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 19:48 anna [this message]
2022-02-08 20:12 ` Linus Torvalds
2022-02-08 20:20 ` Anna Schumaker
2022-02-08 22:30 ` 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=20220208194800.482704-1-anna@kernel.org \
--to=anna@kernel.org \
--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
all inboxes | Powered by JetHome®