public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,  drosen@google.com
Subject: Re: [PATCH] ext4: introduce linear search for dentries
Date: Wed, 12 Feb 2025 16:02:21 -0500	[thread overview]
Message-ID: <87h64yx4f6.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <20250212164448.111211-1-tytso@mit.edu> (Theodore Ts'o's message of "Wed, 12 Feb 2025 11:44:48 -0500")

"Theodore Ts'o" <tytso@mit.edu> writes:

> This patch addresses an issue where some files in case-insensitive
> directories become inaccessible due to changes in how the kernel
> function, utf8_casefold(), generates case-folded strings from the
> commit 5c26d2f1d3f5 ("unicode: Don't special case ignorable code
> points").
>
> There are good reasons why this change should be made; it's actually
> quite stupid that Unicode seems to think that the characters ❤ and ❤️
> should be casefolded.  Unfortimately because of the backwards
> compatibility issue, this commit was reverted in 231825b2e1ff.
>
> This problem is addressed by instituting a brute-force linear fallback
> if a lookup fails on case-folded directory, which does result in a
> performance hit when looking up files affected by the changing how
> thekernel treats ignorable Uniode characters, or when attempting to
> look up non-existent file names.  So this fallback can be disabled by
> setting an encoding flag if in the future, the system administrator or
> the manufacturer of a mobile handset or tablet can be sure that there
> was no opportunity for a kernel to insert file names with incompatible
> encodings.
>
> Fixes: 5c26d2f1d3f5 ("unicode: Don't special case ignorable code points")
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>

Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>

-- 
Gabriel Krisman Bertazi

  reply	other threads:[~2025-02-12 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12 16:44 [PATCH] ext4: introduce linear search for dentries Theodore Ts'o
2025-02-12 21:02 ` Gabriel Krisman Bertazi [this message]
2025-02-13 20:10 ` [PATCH -v2] " Theodore Ts'o
2025-02-13 20:17   ` Eric Biggers
2025-02-19 20:30   ` Andreas Dilger
2025-02-19 21:43     ` Gabriel Krisman Bertazi
2025-02-20  1:58       ` Andreas Dilger
2025-02-20 14:46         ` Theodore Ts'o

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=87h64yx4f6.fsf@mailhost.krisman.be \
    --to=krisman@suse.de \
    --cc=drosen@google.com \
    --cc=linux-ext4@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