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] First round of NFSD fixes for v7.0
Date: Mon, 2 Mar 2026 09:11:29 -0500 [thread overview]
Message-ID: <20260302141130.9098-1-cel@kernel.org> (raw)
The following changes since commit e939bd675634fd52d559b90e2cf58333e16afea8:
NFSD: Add POSIX ACL file attributes to SUPPATTR bitmasks (2026-01-29 09:48:33 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-7.0-1
for you to fetch changes up to 364410170ab33f6e7ef0eb2afb12bf89b0feb3a6:
nfsd: report the requested maximum number of threads instead of number running (2026-02-24 10:27:51 -0500)
----------------------------------------------------------------
nfsd-7.0 fixes:
NFSD fixes that arrived too late for the 7.0 merge window.
Fixes for commits merged in 7.0:
- Restore previous nfsd thread count reporting behavior
Issues that need expedient stable backports:
- Fix credential reference leaks in the NFSD netlink admin protocol
----------------------------------------------------------------
Jeff Layton (1):
nfsd: report the requested maximum number of threads instead of number running
Kuniyuki Iwashima (2):
nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().
nfsd: Fix cred ref leak in nfsd_nl_listener_set_doit().
Documentation/netlink/specs/nfsd.yaml | 4 ++--
fs/nfsd/nfsctl.c | 22 +++++++++++-----------
fs/nfsd/nfssvc.c | 7 ++++---
3 files changed, 17 insertions(+), 16 deletions(-)
next reply other threads:[~2026-03-02 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:11 Chuck Lever [this message]
2026-03-02 17:48 ` [GIT PULL] First round of NFSD fixes for v7.0 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=20260302141130.9098-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