From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Eugen Hristev <eugen.hristev@collabora.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, jaegeuk@kernel.org,
chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, viro@zeniv.linux.org.uk,
brauner@kernel.org, jack@suse.cz,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [PATCH v10 3/8] libfs: Introduce case-insensitive string comparison helper
Date: Tue, 20 Feb 2024 09:59:44 -0500 [thread overview]
Message-ID: <871q97b2qn.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <fb32fc72-5434-4852-b7e9-f63fc03a8248@collabora.com> (Eugen Hristev's message of "Tue, 20 Feb 2024 09:36:40 +0200")
Eugen Hristev <eugen.hristev@collabora.com> writes:
> Okay, I am changing it.
>
> By the way, is this supposed to work like this on case-insensitive directories ?
>
> user@debian-rockchip-rock5b-rk3588:~$ ls -la /media/CI_dir/*cuc
> ls: cannot access '/media/CI_dir/*cuc': No such file or directory
> user@debian-rockchip-rock5b-rk3588:~$ ls -la /media/CI_dir/*CUC
> -rw-r--r-- 1 root root 0 Feb 12 17:47 /media/CI_dir/CUC
> user@debian-rockchip-rock5b-rk3588:~$ ls -la /media/CI_dir/cuc
> -rw-r--r-- 1 root root 0 Feb 12 17:47 /media/CI_dir/cuc
> user@debian-rockchip-rock5b-rk3588:~$
>
>
> basically wildcards don't work.
Yes, at least from a kernel point of view. Your shell does wildcards in
userspace, probably by doing getdents and then comparing with possible
matches. Since the shell itself is not case-insensitive aware, its
comparison is case-sensitive, and you get these apparent weird
semantics.
Not ideal from a user point of view. But not a kernel bug. If it
pushes people away from using case-insensitive directories in their
day-to-day work and leave it to only be used by Windows compatibility
layers, maybe that's a win? :)
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2024-02-20 14:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 4:26 [PATCH v10 0/8] Eugen Hristev
2024-02-15 4:26 ` [PATCH v10 1/8] ext4: Simplify the handling of cached insensitive names Eugen Hristev
2024-02-15 4:26 ` [PATCH v10 2/8] f2fs: " Eugen Hristev
2024-02-15 4:26 ` [PATCH v10 3/8] libfs: Introduce case-insensitive string comparison helper Eugen Hristev
2024-02-16 16:12 ` Gabriel Krisman Bertazi
2024-02-19 4:22 ` Eugen Hristev
2024-02-19 14:55 ` Gabriel Krisman Bertazi
2024-02-20 7:36 ` Eugen Hristev
2024-02-20 14:59 ` Gabriel Krisman Bertazi [this message]
2024-02-15 4:26 ` [PATCH v10 4/8] ext4: Reuse generic_ci_match for ci comparisons Eugen Hristev
2024-02-15 4:26 ` [PATCH v10 5/8] f2fs: " Eugen Hristev
2024-02-15 4:26 ` [PATCH v10 6/8] ext4: Log error when lookup of encoded dentry fails Eugen Hristev
2024-02-15 4:26 ` [PATCH v10 7/8] ext4: Move CONFIG_UNICODE defguards into the code flow Eugen Hristev
2024-03-22 22:11 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-02-15 4:26 ` [PATCH v10 8/8] f2fs: " Eugen Hristev
2024-07-24 2:16 ` [f2fs-dev] [PATCH v10 0/8] patchwork-bot+f2fs
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=871q97b2qn.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=eugen.hristev@collabora.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).