From: Chuck Lever <cel@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>
Subject: [GIT PULL] More NFSD fixes for 7.1-rc
Date: Tue, 26 May 2026 15:46:42 -0400 [thread overview]
Message-ID: <20260526194642.108872-1-cel@kernel.org> (raw)
The following changes since commit 4f8ef58c10bfe5f86a643c7c8331b37e69e3dae1:
NFSD: Fix infinite loop in layout state revocation (2026-05-10 12:41:08 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-7.1-2
for you to fetch changes up to 0b474240327cebeff08ad429e8ed3cfc6c8ee816:
lockd: fix TEST handling when not all permissions are available. (2026-05-21 17:08:47 -0400)
----------------------------------------------------------------
nfsd-7.1 fixes:
Issues reported with v7.1-rc:
- Tighten bounds checking for sunrpc cache hash tables
- Don't report key material in the ftrace log
Issues that need expedient stable backports:
- Fix lockd's implementation of the NLM TEST procedure
----------------------------------------------------------------
Chuck Lever (2):
sunrpc: prevent out-of-bounds read in __cache_seq_start()
NFSD: Report whether fh_key was actually updated
NeilBrown (1):
lockd: fix TEST handling when not all permissions are available.
fs/lockd/lockd.h | 2 +-
fs/lockd/svc4proc.c | 9 +++++++--
fs/lockd/svclock.c | 4 +---
fs/lockd/svcproc.c | 15 ++++++++++++---
fs/lockd/svcsubs.c | 31 +++++++++++++++++++++----------
fs/nfsd/nfsctl.c | 18 ++++++++++++++----
fs/nfsd/trace.h | 16 +++++++---------
net/sunrpc/cache.c | 3 +++
8 files changed, 66 insertions(+), 32 deletions(-)
next reply other threads:[~2026-05-26 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 19:46 Chuck Lever [this message]
2026-05-26 23:41 ` [GIT PULL] More NFSD fixes for 7.1-rc 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=20260526194642.108872-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=jlayton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.