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] Second round of NFSD fixes for v7.0-rc
Date: Wed, 18 Mar 2026 17:14:47 -0400 [thread overview]
Message-ID: <20260318211447.1808-1-cel@kernel.org> (raw)
The following changes since commit 364410170ab33f6e7ef0eb2afb12bf89b0feb3a6:
nfsd: report the requested maximum number of threads instead of number running (2026-02-24 10:27:51 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-7.0-2
for you to fetch changes up to 5133b61aaf437e5f25b1b396b14242a6bb0508e2:
nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (2026-03-16 16:58:01 -0400)
----------------------------------------------------------------
nfsd-7.0 fixes:
Issues that need expedient stable backports:
- Fix cache_request leak in cache_release()
- Fix heap overflow in the NFSv4.0 LOCK replay cache
- Hold net reference for the lifetime of /proc/fs/nfs/exports fd
- Defer sub-object cleanup in export "put" callbacks
----------------------------------------------------------------
Chuck Lever (2):
NFSD: Defer sub-object cleanup in export put callbacks
NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd
Jeff Layton (2):
sunrpc: fix cache_request leak in cache_release
nfsd: fix heap overflow in NFSv4.0 LOCK replay cache
fs/nfsd/export.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++--------
fs/nfsd/export.h | 7 ++++--
fs/nfsd/nfs4xdr.c | 9 ++++++--
fs/nfsd/nfsctl.c | 22 ++++++++++++++++---
fs/nfsd/state.h | 17 ++++++++++-----
net/sunrpc/cache.c | 26 +++++++++++++++++-----
6 files changed, 118 insertions(+), 26 deletions(-)
next reply other threads:[~2026-03-18 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 21:14 Chuck Lever [this message]
2026-03-18 21:35 ` [GIT PULL] Second round of NFSD fixes for v7.0-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=20260318211447.1808-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox