From: Chuck Lever <cel@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-nfs@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>
Subject: [GIT PULL] More NFSD fixes for v6.19-rc
Date: Tue, 30 Dec 2025 20:40:18 -0500 [thread overview]
Message-ID: <20251231014018.2635778-1-cel@kernel.org> (raw)
The following changes since commit 913f7cf77bf14c13cfea70e89bcb6d0b22239562:
NFSD: NFSv4 file creation neglects setting ACL (2025-12-18 11:19:11 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.19-2
for you to fetch changes up to 1f941b2c23fd34c6f3b76d36f9d0a2528fa92b8f:
nfsd: Drop the client reference in client_states_open() (2025-12-24 21:33:12 -0500)
----------------------------------------------------------------
nfsd-6.19 fixes:
A set of NFSD fixes that arrived just a bit late for the 6.19 merge
window.
Issues reported with v6.19-rc:
- Avoid unnecessarily breaking a timestamp delegation
Issues that need expedient stable backports:
- Fix a crasher in nlm4svc_proc_test()
- Fix nfsd_file reference leak during write delegation
- Fix error flow in client_states_open()
----------------------------------------------------------------
Chuck Lever (1):
nfsd: fix nfsd_file reference leak in nfsd4_add_rdaccess_to_wrdeleg()
Haoxiang Li (1):
nfsd: Drop the client reference in client_states_open()
Jeff Layton (1):
nfsd: use ATTR_DELEG in nfsd4_finalize_deleg_timestamps()
NeilBrown (1):
lockd: fix vfs_test_lock() calls
fs/lockd/svc4proc.c | 4 +---
fs/lockd/svclock.c | 21 ++++++++++++---------
fs/lockd/svcproc.c | 5 +----
fs/locks.c | 12 ++++++++++--
fs/nfsd/nfs4state.c | 20 ++++++++++++++------
5 files changed, 38 insertions(+), 24 deletions(-)
next reply other threads:[~2025-12-31 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 1:40 Chuck Lever [this message]
2025-12-31 5:33 ` 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=20251231014018.2635778-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
all inboxes | Powered by JetHome®