All of lore.kernel.org
 help / color / mirror / Atom feed
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 v6.16
Date: Sat, 21 Jun 2025 11:13:59 -0400	[thread overview]
Message-ID: <20250621151359.499129-1-cel@kernel.org> (raw)

The following changes since commit 425364dc49f050b6008b43408aa96d42105a9c1d:

  xdrgen: Fix code generated for counted arrays (2025-05-16 10:58:48 -0400)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.16-1

for you to fetch changes up to 94d10a4dba0bc482f2b01e39f06d5513d0f75742:

  sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (2025-06-19 09:35:45 -0400)

----------------------------------------------------------------
nfsd-6.16 fixes:

- Two fixes for commits in the nfsd-6.16 merge
- One fix for the recently-added NFSD netlink facility
- One fix for a remote SunRPC crasher

----------------------------------------------------------------
Benjamin Coddington (1):
      SUNRPC: Cleanup/fix initial rq_pages allocation

Chuck Lever (1):
      NFSD: Avoid corruption of a referring call list

Jeff Layton (2):
      nfsd: use threads array as-is in netlink interface
      sunrpc: handle SVC_GARBAGE during svc auth processing as auth error

 fs/nfsd/nfs4callback.c |  1 +
 fs/nfsd/nfsctl.c       |  5 ++---
 net/sunrpc/svc.c       | 17 +++--------------
 3 files changed, 6 insertions(+), 17 deletions(-)

             reply	other threads:[~2025-06-21 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-21 15:13 Chuck Lever [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-21 15:13 [GIT PULL] First round of NFSD fixes for v6.16 Chuck Lever
2025-06-21 16:36 ` 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=20250621151359.499129-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.