diff options
author | 2025-02-07 23:08:02 -0500 | |
---|---|---|
committer | 2025-02-13 15:05:53 -0500 | |
commit | 9e28059d56649a7212d5b3f8751ec021154ba3dd (patch) | |
tree | 9fac8e85a3b73f9da30eed155a425e6aa3f445fd /tools/perf/scripts/python/export-to-postgresql.py | |
parent | jbd2: Avoid long replay times due to high number or revoke blocks (diff) | |
download | wireguard-linux-9e28059d56649a7212d5b3f8751ec021154ba3dd.tar.xz wireguard-linux-9e28059d56649a7212d5b3f8751ec021154ba3dd.zip |
ext4: introduce linear search for dentries
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>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions