From: Chuck Lever <cel@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Cc: <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-cifs@vger.kernel.org, <linux-nfs@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
hirofumi@mail.parknet.co.jp, linkinjeon@kernel.org,
sj1557.seo@samsung.com, yuezhang.mo@sony.com,
almaz.alexandrovich@paragon-software.com, slava@dubeyko.com,
glaubitz@physik.fu-berlin.de, frank.li@vivo.com, tytso@mit.edu,
adilger.kernel@dilger.ca, cem@kernel.org, sfrench@samba.org,
pc@manguebit.org, ronniesahlberg@gmail.com,
sprasad@microsoft.com, trondmy@kernel.org, anna@kernel.org,
jaegeuk@kernel.org, chao@kernel.org, hansg@kernel.org,
senozhatsky@chromium.org, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v5 11/16] f2fs: Add case sensitivity reporting to fileattr_get
Date: Fri, 16 Jan 2026 09:46:10 -0500 [thread overview]
Message-ID: <20260116144616.2098618-12-cel@kernel.org> (raw)
In-Reply-To: <20260116144616.2098618-1-cel@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
NFS and other remote filesystem protocols need to determine
whether a local filesystem performs case-insensitive lookups
so they can provide correct semantics to clients. Without
this information, f2fs exports cannot properly advertise
their filename case behavior.
Report f2fs case sensitivity behavior via the file_kattr
boolean fields. Like ext4, f2fs supports per-directory case
folding via the casefold flag (IS_CASEFOLDED). Files are
always case-preserving.
Reviewed-by: Chao Yu <chao@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
fs/f2fs/file.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index d7047ca6b98d..5d4c129c9802 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -3439,6 +3439,12 @@ int f2fs_fileattr_get(struct dentry *dentry, struct file_kattr *fa)
if (f2fs_sb_has_project_quota(F2FS_I_SB(inode)))
fa->fsx_projid = from_kprojid(&init_user_ns, fi->i_projid);
+ /*
+ * f2fs preserves case (the default). If this inode is a
+ * casefolded directory, report case-insensitive; otherwise
+ * report case-sensitive (standard POSIX behavior).
+ */
+ fa->case_insensitive = IS_CASEFOLDED(inode);
return 0;
}
--
2.52.0
next prev parent reply other threads:[~2026-01-16 14:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 14:45 [PATCH v5 00/16] Exposing case folding behavior Chuck Lever
2026-01-16 14:46 ` [PATCH v5 01/16] fs: Add case sensitivity info to file_kattr Chuck Lever
2026-01-16 16:28 ` Darrick J. Wong
2026-01-16 14:46 ` [PATCH v5 02/16] fat: Implement fileattr_get for case sensitivity Chuck Lever
2026-01-16 14:46 ` [PATCH v5 03/16] exfat: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 04/16] ntfs3: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 05/16] hfs: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 06/16] hfsplus: Report case sensitivity in fileattr_get Chuck Lever
2026-01-16 14:46 ` [PATCH v5 07/16] ext4: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 08/16] xfs: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 09/16] cifs: Implement fileattr_get for case sensitivity Chuck Lever
2026-01-16 14:46 ` [PATCH v5 10/16] nfs: " Chuck Lever
2026-01-16 14:46 ` Chuck Lever [this message]
2026-01-16 14:46 ` [PATCH v5 12/16] vboxsf: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 13/16] isofs: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 14/16] nfsd: Report export case-folding via NFSv3 PATHCONF Chuck Lever
2026-01-16 14:46 ` [PATCH v5 15/16] nfsd: Implement NFSv4 FATTR4_CASE_INSENSITIVE and FATTR4_CASE_PRESERVING Chuck Lever
2026-01-16 14:46 ` [PATCH v5 16/16] ksmbd: Report filesystem case sensitivity via FS_ATTRIBUTE_INFORMATION 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=20260116144616.2098618-12-cel@kernel.org \
--to=cel@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=anna@kernel.org \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=chao@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hansg@kernel.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.org \
--cc=sj1557.seo@samsung.com \
--cc=slava@dubeyko.com \
--cc=sprasad@microsoft.com \
--cc=trondmy@kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=yuezhang.mo@sony.com \
/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