From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
Chuck Lever <cel@kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Volker Lendecke <Volker.Lendecke@sernet.de>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [RFC PATCH] fs: Plumb case sensitivity bits into statx
Date: Fri, 10 Oct 2025 15:06:05 -0400 [thread overview]
Message-ID: <87v7kmziea.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <20251010144938.GB6174@frogsfrogsfrogs> (Darrick J. Wong's message of "Fri, 10 Oct 2025 07:49:38 -0700")
"Darrick J. Wong" <djwong@kernel.org> writes:
> n00b question here: Can you enable (or disable) casefolding and the
> folding scheme used? My guess is that one ought to be able to do that
> either (a) on an empty directory or (b) by reindexing the entire
> directory if the filesystem supports that kind of thing? But hey, it's
> not like xfs supports any of that. ;)
We only support enabling/disabling on an empty directory.
Disabling casefolding on an already populated directory would be easier
to do - just re-index, as you said. But to enable it, you'd need to
handle cases where you have two different files that now have the "same"
name (differing only by case). Then, which one you'll get is quite
unpredictable (perhaps, the order the dirent appears on-disk, etc).
So we just don't allow it.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2025-10-10 19:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 15:11 [RFC PATCH] fs: Plumb case sensitivity bits into statx Chuck Lever
2025-09-25 15:50 ` Amir Goldstein
2025-10-03 15:24 ` Gabriel Krisman Bertazi
2025-10-03 15:34 ` Chuck Lever
2025-10-03 20:43 ` Gabriel Krisman Bertazi
2025-10-03 21:05 ` Chuck Lever
2025-10-03 21:11 ` ronnie sahlberg
2025-10-03 21:15 ` Gabriel Krisman Bertazi
2025-10-04 17:27 ` Chuck Lever
2025-10-06 11:19 ` Christian Brauner
2025-10-07 17:18 ` Gabriel Krisman Bertazi
2025-10-10 11:11 ` Christian Brauner
2025-10-10 12:43 ` Chuck Lever
2025-10-21 11:54 ` Christian Brauner
2025-10-10 14:49 ` Darrick J. Wong
2025-10-10 19:06 ` Gabriel Krisman Bertazi [this message]
2025-10-03 17:19 ` Steve French
2025-09-26 4:20 ` Christoph Hellwig
2025-09-26 13:02 ` Chuck Lever
2025-09-26 10:00 ` Jeff Layton
2025-09-26 13:05 ` 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=87v7kmziea.fsf@mailhost.krisman.be \
--to=gabriel@krisman.be \
--cc=Volker.Lendecke@sernet.de \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=djwong@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).