From: Chuck Lever <cel@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org, <linux-nfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
hirofumi@mail.parknet.co.jp,
almaz.alexandrovich@paragon-software.com, tytso@mit.edu,
adilger.kernel@dilger.ca, Volker.Lendecke@sernet.de,
Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v2 4/6] ext4: Report case sensitivity in fileattr_get
Date: Thu, 11 Dec 2025 10:21:14 -0500 [thread overview]
Message-ID: <20251211152116.480799-5-cel@kernel.org> (raw)
In-Reply-To: <20251211152116.480799-1-cel@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
Report ext4's case sensitivity behavior via file_kattr.case_info.
ext4 always preserves case at rest.
Case sensitivity is a per-directory setting in ext4. If the queried
inode is a casefolded directory, report Unicode case-insensitive
matching; otherwise report case-sensitive (standard POSIX behavior).
This enables file_getattr to report the case sensitivity behavior of
individual directories within an ext4 filesystem.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
fs/ext4/ioctl.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/fs/ext4/ioctl.c b/fs/ext4/ioctl.c
index a93a7baae990..d760657bb9e2 100644
--- a/fs/ext4/ioctl.c
+++ b/fs/ext4/ioctl.c
@@ -996,6 +996,18 @@ int ext4_fileattr_get(struct dentry *dentry, struct file_kattr *fa)
if (ext4_has_feature_project(inode->i_sb))
fa->fsx_projid = from_kprojid(&init_user_ns, ei->i_projid);
+ /*
+ * ext4 always preserves case. If this inode is a casefolded
+ * directory, report Unicode case-insensitive; otherwise
+ * report case-sensitive (standard POSIX behavior).
+ */
+ if (IS_CASEFOLDED(inode))
+ fa->case_info = FILEATTR_CASEFOLD_UNICODE |
+ FILEATTR_CASE_PRESERVING;
+ else
+ fa->case_info = FILEATTR_CASEFOLD_NONE |
+ FILEATTR_CASE_PRESERVING;
+
return 0;
}
--
2.52.0
next prev parent reply other threads:[~2025-12-11 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 15:21 [PATCH v2 0/6] Exposing case folding behavior Chuck Lever
2025-12-11 15:21 ` [PATCH v2 1/6] fs: Add case sensitivity info to file_kattr Chuck Lever
2025-12-11 23:41 ` Eric Biggers
2025-12-12 1:16 ` Chuck Lever
2025-12-12 2:18 ` Theodore Tso
2025-12-12 15:08 ` Chuck Lever
2025-12-12 21:23 ` Theodore Tso
2025-12-12 22:49 ` Trond Myklebust
2025-12-13 16:43 ` Chuck Lever
2025-12-15 12:37 ` Christian Brauner
2025-12-11 15:21 ` [PATCH v2 2/6] fat: Implement fileattr_get for case sensitivity Chuck Lever
2025-12-12 4:42 ` OGAWA Hirofumi
2025-12-11 15:21 ` [PATCH v2 3/6] ntfs3: " Chuck Lever
2025-12-11 15:21 ` Chuck Lever [this message]
2025-12-11 15:21 ` [PATCH v2 5/6] nfsd: Report export case-folding via NFSv3 PATHCONF Chuck Lever
2025-12-11 15:21 ` [PATCH v2 6/6] nfsd: Implement NFSv4 FATTR4_CASE_INSENSITIVE and FATTR4_CASE_PRESERVING Chuck Lever
2025-12-12 5:20 ` [PATCH v2 0/6] Exposing case folding behavior Christoph Hellwig
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=20251211152116.480799-5-cel@kernel.org \
--to=cel@kernel.org \
--cc=Volker.Lendecke@sernet.de \
--cc=adilger.kernel@dilger.ca \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).