From: Chuck Lever <cel@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 0/7] Fixes for vfs/vfs-7.2.casefold
Date: Fri, 15 May 2026 11:35:08 -0400 [thread overview]
Message-ID: <20260515153515.362266-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
Address review comments for the series in the vfs/vfs-7.2.casefold
branch.
Chuck Lever (7):
tools headers UAPI: Sync case-sensitivity flags from linux/fs.h
nfs: Avoid transient zeroed case capability bits during probe
nfs: Skip pathconf probe when neither field is consumed
fs: Clarify FS_CASEFOLD_FL semantics in UAPI header
nfsd: Use kernel credentials for case-info probe
nfsd: Map -ESTALE from case probe to NFS3ERR_STALE
nfsd: Cap case-folding probe cost across READDIR entries
fs/nfs/client.c | 29 ++++++----
fs/nfsd/nfs3proc.c | 3 +
fs/nfsd/nfs4xdr.c | 55 ++++++++++++++++---
fs/nfsd/vfs.c | 4 +-
fs/nfsd/xdr4.h | 14 +++++
include/uapi/linux/fs.h | 11 +++-
.../perf/trace/beauty/include/uapi/linux/fs.h | 7 +++
7 files changed, 98 insertions(+), 25 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-15 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 15:35 Chuck Lever [this message]
2026-05-15 15:35 ` [PATCH 1/7] tools headers UAPI: Sync case-sensitivity flags from linux/fs.h Chuck Lever
2026-05-15 15:35 ` [PATCH 2/7] nfs: Avoid transient zeroed case capability bits during probe Chuck Lever
2026-05-15 15:35 ` [PATCH 3/7] nfs: Skip pathconf probe when neither field is consumed Chuck Lever
2026-05-15 15:35 ` [PATCH 4/7] fs: Clarify FS_CASEFOLD_FL semantics in UAPI header Chuck Lever
2026-05-15 15:35 ` [PATCH 5/7] nfsd: Use kernel credentials for case-info probe Chuck Lever
2026-05-15 15:35 ` [PATCH 6/7] nfsd: Map -ESTALE from case probe to NFS3ERR_STALE Chuck Lever
2026-05-15 15:35 ` [PATCH 7/7] nfsd: Cap case-folding probe cost across READDIR entries 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=20260515153515.362266-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@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