From: "Theodore Tso" <tytso@mit.edu>
To: David Laight <david.laight.linux@gmail.com>
Cc: Gabriel Krisman Bertazi <krisman@suse.de>,
Sarthak Kukreti <sarthakkukreti@google.com>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Gabriel Krisman Bertazi <krisman@collabora.co.uk>,
Eric Biggers <ebiggers@google.com>,
Dmitry Torokhov <dtor@google.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] libfs: reject casefolded names that fold to ".", "..", or empty
Date: Tue, 17 Nov 2026 09:54:32 -0500 [thread overview]
Message-ID: <avxe5v6r1C7ZG7E2@mit.edu> (raw)
In-Reply-To: <20261117084727.0cfa196a@pumpkin>
On Tue, Nov 17, 2026 at 08:47:27AM -0500, David Laight wrote:
> > Sigh... I really think these characters are *evil*. I wonder if we
> > should simply drop those code points unconditionally when they are fed
> > to the kernel --- not only folding to themselves, but *not* preserving
> > them when a misguided application tries to create a file with one of
> > these misbegotten Unicode charactesr.
>
> Doesn't that assume that filenames are UTF8 rather than just sequences
> of bytes with everything except '\0' and '/' being valid.
> Casefolding is itself so evil/impossible it shouldn't have been allowed.
We would only do this if casefolding is enabled. For better or for
worse, it's better than what it replaced which was this terrible
wrapfs hack that was a trivial to trigger deadlocks using fsstress ---
which was even more evil.
The other way we can deal with this is that if case folding is
enabled, we change the VFS to call the case-folding for incoming
filename *before* it does its special case checking for '.' and '..'
if casefolding is enabled.
- Ted
next prev parent reply other threads:[~2026-11-17 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 6:53 [PATCH 0/3] fs: " Sarthak Kukreti
2026-11-13 6:53 ` [PATCH 1/3] libfs: " Sarthak Kukreti
2026-11-16 19:34 ` Gabriel Krisman Bertazi
2026-11-16 20:05 ` Eric Biggers
2026-11-17 2:00 ` Theodore Tso
2026-11-17 8:47 ` David Laight
2026-11-17 14:54 ` Theodore Tso [this message]
2026-11-17 2:44 ` Sarthak Kukreti
2026-11-13 6:53 ` [PATCH 2/3] ext4: " Sarthak Kukreti
2026-11-13 6:53 ` [PATCH 3/3] f2fs: " Sarthak Kukreti
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=avxe5v6r1C7ZG7E2@mit.edu \
--to=tytso@mit.edu \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=dtor@google.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=krisman@collabora.co.uk \
--cc=krisman@suse.de \
--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=sarthakkukreti@google.com \
--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
all inboxes | Powered by JetHome®