From: Chuck Lever <cel@kernel.org>
To: <stable@vger.kernel.org>
Cc: <linux-nfs@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 6.6.y 0/4] NFSD: NFSv4 file creation neglects setting ACL
Date: Sat, 3 Jan 2026 14:38:50 -0500 [thread overview]
Message-ID: <20260103193854.2954342-1-cel@kernel.org> (raw)
In-Reply-To: 2025122941-civic-revered-b250@gregkh
From: Chuck Lever <chuck.lever@oracle.com>
I received an automated report that patch "NFSD: NFSv4 file creation
neglects setting ACL" failed to apply to the 6.6-stable tree. This
series is my attempt to address that failure.
- First, applied several pre-requisite patches
- LLM agent review for possible regressions reported no issues
- CI testing reported no regressions
Chuck Lever (4):
nfsd: convert to new timestamp accessors
nfsd: Fix NFSv3 atomicity bugs in nfsd_setattr()
nfsd: set security label during create operations
NFSD: NFSv4 file creation neglects setting ACL
fs/nfsd/nfs3proc.c | 10 ++++++----
fs/nfsd/nfs3xdr.c | 5 +----
fs/nfsd/nfs4proc.c | 11 +++++------
fs/nfsd/nfs4state.c | 2 +-
fs/nfsd/nfsctl.c | 2 +-
fs/nfsd/nfsproc.c | 6 +++---
fs/nfsd/vfs.c | 22 ++++++++++++++--------
fs/nfsd/vfs.h | 11 ++++++++++-
fs/nfsd/xdr3.h | 2 +-
9 files changed, 42 insertions(+), 29 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-03 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 19:38 Chuck Lever [this message]
2026-01-03 19:38 ` [PATCH 6.6.y 1/4] nfsd: convert to new timestamp accessors Chuck Lever
2026-01-08 11:03 ` Greg Kroah-Hartman
2026-01-08 14:25 ` Chuck Lever
2026-01-08 15:27 ` Greg Kroah-Hartman
2026-01-08 12:33 ` Greg Kroah-Hartman
2026-01-03 19:38 ` [PATCH 6.6.y 2/4] nfsd: Fix NFSv3 atomicity bugs in nfsd_setattr() Chuck Lever
2026-01-03 19:38 ` [PATCH 6.6.y 3/4] nfsd: set security label during create operations Chuck Lever
2026-01-03 19:38 ` [PATCH 6.6.y 4/4] NFSD: NFSv4 file creation neglects setting ACL Chuck Lever
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=20260103193854.2954342-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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