From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Cedric Blancher <cedric.blancher@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: LInux NFSv4.1 client and server- case insensitive filesystems supported?
Date: Mon, 09 Jun 2025 11:28:46 -0400 [thread overview]
Message-ID: <875xh5ylw1.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <a44ebcd9-436b-436f-a6f5-dea8958aaf2f@oracle.com> (Chuck Lever's message of "Sun, 8 Jun 2025 17:52:36 -0400")
Chuck Lever <chuck.lever@oracle.com> writes:
> On 6/8/25 4:52 PM, Theodore Ts'o wrote:
>> On Sun, Jun 08, 2025 at 12:29:30PM -0400, Chuck Lever wrote:
>>>
>>> For some reason I thought case-insensitivity support was merged more
>>> recently than that. I recall it first appearing as a session at LSF in
>>> Park City, but maybe that one was in 2018.
Hi Chuck,
The first LSF discussion on this implementation was Park City, 2018. It
was merged early 2019.
> Ted, do you happen to know if there are any fstests that exercise case-
> insensitive lookups? I would not regard that simple test as "job done!
> put pencil down!" :-)
generic/556 tests basic semantics and many corner cases of casefolded
lookups.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2025-06-09 15:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 17:58 LInux NFSv4.1 client and server- case insensitive filesystems supported? Cedric Blancher
2025-06-04 18:52 ` Cedric Blancher
2025-06-07 18:30 ` Chuck Lever
2025-06-07 22:39 ` Theodore Ts'o
2025-06-08 10:19 ` Jeff Layton
2025-06-08 16:29 ` Chuck Lever
2025-06-08 20:52 ` Theodore Ts'o
2025-06-08 21:52 ` Chuck Lever
2025-06-09 15:28 ` Gabriel Krisman Bertazi [this message]
2025-06-09 15:50 ` Theodore Ts'o
2025-06-09 16:41 ` Chuck Lever
2025-06-09 5:57 ` Christoph Hellwig
2025-06-09 14:16 ` Chuck Lever
2025-06-10 5:34 ` Christoph Hellwig
2025-09-09 16:06 ` NFSv4.x export options to mark export as case-insensitive, case-preserving? " Cedric Blancher
2025-09-09 16:11 ` Cedric Blancher
2025-09-09 16:11 ` Chuck Lever
2025-09-09 16:33 ` Cedric Blancher
2025-09-09 19:32 ` Chuck Lever
2025-09-10 10:44 ` Roland Mainz
2025-09-10 13:37 ` Rick Macklem
2025-09-11 8:07 ` fattr4_archive "deprecated" ? " Cedric Blancher
2025-09-11 15:01 ` Rick Macklem
2025-09-11 15:26 ` Trond Myklebust
2025-09-11 15:33 ` Cedric Blancher
2025-09-11 15:36 ` Cedric Blancher
2025-09-11 16:08 ` Cedric Blancher
2025-09-10 11:10 ` Jeff Layton
2025-09-10 14:14 ` Chuck Lever
2025-09-10 14:30 ` Jeff Layton
2025-09-10 14:35 ` Chuck Lever
2025-09-11 6:52 ` Cedric Blancher
2025-09-11 6:49 ` Cedric Blancher
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=875xh5ylw1.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=cedric.blancher@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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