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 v6.18-rc
Date: Tue, 28 Oct 2025 15:06:06 -0400 [thread overview]
Message-ID: <20251028190606.43007-1-cel@kernel.org> (raw)
The following changes since commit 4b47a8601b71ad98833b447d465592d847b4dc77:
NFSD: Define a proc_layoutcommit for the FlexFiles layout type (2025-10-10 12:53: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-2
for you to fetch changes up to 3e7f011c255582d7c914133785bbba1990441713:
Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND" (2025-10-21 11:03:50 -0400)
----------------------------------------------------------------
nfsd-6.18 fixes:
Issues reported with v6.18-rc:
- Revert the patch that removed the cap on MAX_OPS_PER_COMPOUND
- Address a kernel build issue
Issues that need expedient stable backports:
- Fix crash when a client queries new attributes on forechannel
- Fix rare NFSD crash when tracing is enabled
----------------------------------------------------------------
Chuck Lever (3):
NFSD: Define actions for the new time_deleg FATTR4 attributes
NFSD: Fix crash in nfsd4_read_release()
Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND"
Nathan Chancellor (1):
nfsd: Avoid strlen conflict in nfsd4_encode_components_esc()
fs/nfsd/nfs4proc.c | 21 ++++++++++++++++-----
fs/nfsd/nfs4state.c | 1 +
fs/nfsd/nfs4xdr.c | 21 ++++++++++++++-------
fs/nfsd/nfsd.h | 3 +++
fs/nfsd/xdr4.h | 1 +
5 files changed, 35 insertions(+), 12 deletions(-)
next reply other threads:[~2025-10-28 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 19:06 Chuck Lever [this message]
2025-10-28 21:50 ` [GIT PULL] More NFSD fixes for v6.18-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=20251028190606.43007-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.