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] Third round of fixes for NFSD (6.19)
Date: Tue, 6 Jan 2026 10:59:02 -0500 [thread overview]
Message-ID: <20260106155902.3706718-1-cel@kernel.org> (raw)
The following changes since commit 1f941b2c23fd34c6f3b76d36f9d0a2528fa92b8f:
nfsd: Drop the client reference in client_states_open() (2025-12-24 21:33:12 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.19-3
for you to fetch changes up to 0b88bfa42e5468baff71909c2f324a495318532b:
NFSD: net ref data still needs to be freed even if net hasn't startup (2026-01-02 13:50:14 -0500)
----------------------------------------------------------------
nfsd-6.19 fixes:
A set of NFSD fixes that arrived after the 6.19 merge window.
Issues that need expedient stable backports:
- Remove an invalid NFS status code
- Fix an fstests failure when using pNFS
- Fix a UAF in v4_end_grace()
- Fix the administrative interface used to revoke NFSv4 state
- Fix a memory leak reported by syzbot
----------------------------------------------------------------
Chuck Lever (1):
NFSD: Remove NFSERR_EAGAIN
Edward Adam Davis (1):
NFSD: net ref data still needs to be freed even if net hasn't startup
NeilBrown (2):
nfsd: provide locking for v4_end_grace
nfsd: use correct loop termination in nfsd4_revoke_states()
Olga Kornievskaia (1):
nfsd: check that server is running in unlock_filesystem
Scott Mayhew (1):
NFSD: Fix permission check for read access to executable-only files
fs/nfs_common/common.c | 1 -
fs/nfsd/netns.h | 2 ++
fs/nfsd/nfs4proc.c | 2 +-
fs/nfsd/nfs4state.c | 49 ++++++++++++++++++++++++++++++++++++++++++------
fs/nfsd/nfsctl.c | 12 +++++++++---
fs/nfsd/nfsd.h | 1 -
fs/nfsd/nfssvc.c | 28 +++++++++++++--------------
fs/nfsd/state.h | 6 +++---
fs/nfsd/vfs.c | 4 ++--
include/trace/misc/nfs.h | 2 --
include/uapi/linux/nfs.h | 1 -
11 files changed, 74 insertions(+), 34 deletions(-)
next reply other threads:[~2026-01-06 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:59 Chuck Lever [this message]
2026-01-06 17:28 ` [GIT PULL] Third round of fixes for NFSD (6.19) 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=20260106155902.3706718-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