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-kernel@vger.kernel.org>, <linux-nfs@vger.kernel.org>,
	Jeff Layton <jlayton@kernel.org>
Subject: [GIT PULL] NFSD fixes for v6.19
Date: Tue, 23 Dec 2025 10:36:54 -0500	[thread overview]
Message-ID: <20251223153654.1650936-1-cel@kernel.org> (raw)

The following changes since commit df8c841dd92a7f262ad4fa649aa493b181e02812:

  NFSD: nfsd-io-modes: Separate lists (2025-12-03 09:05:14 -0500)

are available in the Git repository at:

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

for you to fetch changes up to 913f7cf77bf14c13cfea70e89bcb6d0b22239562:

  NFSD: NFSv4 file creation neglects setting ACL (2025-12-18 11:19:11 -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:
- Mark variable __maybe_unused to avoid W=1 build break

Issues that need expedient stable backports:
- NFSv4 file creation neglects setting ACL
- Clear TIME_DELEG in the suppattr_exclcreat bitmap
- Clear SECLABEL in the suppattr_exclcreat bitmap
- Fix memory leak in nfsd_create_serv error paths
- Bound check rq_pages index in inline path
- Return 0 on success from svc_rdma_copy_inline_range
- Use rc_pageoff for memcpy byte offset
- Avoid NULL deref on zero length gss_token in gss_read_proxy_verf

----------------------------------------------------------------
Andy Shevchenko (1):
      nfsd: Mark variable __maybe_unused to avoid W=1 build break

Chuck Lever (3):
      NFSD: Clear SECLABEL in the suppattr_exclcreat bitmap
      NFSD: Clear TIME_DELEG in the suppattr_exclcreat bitmap
      NFSD: NFSv4 file creation neglects setting ACL

Joshua Rogers (4):
      SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf
      svcrdma: use rc_pageoff for memcpy byte offset
      svcrdma: return 0 on success from svc_rdma_copy_inline_range
      svcrdma: bound check rq_pages index in inline path

Shardul Bankar (1):
      nfsd: fix memory leak in nfsd_create_serv error paths

 fs/nfsd/export.c                  | 2 +-
 fs/nfsd/nfs4xdr.c                 | 5 +++++
 fs/nfsd/nfsd.h                    | 8 +++++++-
 fs/nfsd/nfssvc.c                  | 5 ++++-
 fs/nfsd/vfs.h                     | 3 ++-
 net/sunrpc/auth_gss/svcauth_gss.c | 3 ++-
 net/sunrpc/xprtrdma/svc_rdma_rw.c | 7 +++++--
 7 files changed, 26 insertions(+), 7 deletions(-)

             reply	other threads:[~2025-12-23 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23 15:36 Chuck Lever [this message]
2025-12-24 18:55 ` [GIT PULL] NFSD fixes for v6.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=20251223153654.1650936-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.