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] Third round of NFSD fixes for v6.18
Date: Wed, 12 Nov 2025 12:53:54 -0500 [thread overview]
Message-ID: <20251112175354.13059-1-cel@kernel.org> (raw)
The following changes since commit 3e7f011c255582d7c914133785bbba1990441713:
Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND" (2025-10-21 11:03:50 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.18-3
for you to fetch changes up to 324be6dcbf09133a322db16977a84fbb45c16129:
Revert "SUNRPC: Make RPCSEC_GSS_KRB5 select CRYPTO instead of depending on it" (2025-11-10 09:31:52 -0500)
----------------------------------------------------------------
nfsd-6.18 fixes:
Address recently reported issues or issues found at the recent NFS
bake-a-thon held in Raleigh, NC.
Issues reported with v6.18-rc:
- Address a kernel build issue
- Reorder SEQUENCE processing to avoid spurious NFS4ERR_SEQ_MISORDERED
Issues that need expedient stable backports:
- Close a refcount leak exposure
- Report support for NFSv4.2 CLONE correctly
- Fix oops during COPY_NOTIFY processing
- Prevent rare crash after XDR encoding failure
- Prevent crash due to confused or malicious NFSv4.1 client
----------------------------------------------------------------
Chuck Lever (3):
NFSD: Skip close replay processing if XDR encoding fails
NFSD: Never cache a COMPOUND when the SEQUENCE operation fails
Revert "SUNRPC: Make RPCSEC_GSS_KRB5 select CRYPTO instead of depending on it"
NeilBrown (2):
nfsd: fix refcount leak in nfsd_set_fh_dentry()
nfsd: ensure SEQUENCE replay sends a valid reply.
Olga Kornievskaia (2):
nfsd: add missing FATTR4_WORD2_CLONE_BLKSIZE from supported attributes
NFSD: free copynotify stateid in nfs4_free_ol_stateid()
fs/nfsd/nfs4state.c | 68 ++++++++++++++++++++++++++++++++++++++---------------
fs/nfsd/nfs4xdr.c | 5 ++--
fs/nfsd/nfsd.h | 1 +
fs/nfsd/nfsfh.c | 6 ++---
fs/nfsd/xdr4.h | 3 ++-
net/sunrpc/Kconfig | 3 +--
6 files changed, 58 insertions(+), 28 deletions(-)
next reply other threads:[~2025-11-12 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 17:53 Chuck Lever [this message]
2025-11-13 2:44 ` [GIT PULL] Third round of NFSD fixes for v6.18 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=20251112175354.13059-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;
as well as URLs for NNTP newsgroup(s).