]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
Revert "unicode: Don't special case ignorable code points"
authorLinus Torvalds <torvalds@linux-foundation.org>
Wed, 11 Dec 2024 22:11:23 +0000 (14:11 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 14 Dec 2024 18:51:44 +0000 (19:51 +0100)
commit9e9f343615c0eb65b3e3ec6bbbb569147b6e16fe
tree24921a064d334c4c0205c2639e6c8406aba10898
parentd7e6934eb736a205a6893f5e03f245f81518f226
Revert "unicode: Don't special case ignorable code points"

commit 231825b2e1ff6ba799c5eaf396d3ab2354e37c6b upstream.

This reverts commit 5c26d2f1d3f5e4be3e196526bead29ecb139cf91.

It turns out that we can't do this, because while the old behavior of
ignoring ignorable code points was most definitely wrong, we have
case-folding filesystems with on-disk hash values with that wrong
behavior.

So now you can't look up those names, because they hash to something
different.

Of course, it's also entirely possible that in the meantime people have
created *new* files with the new ("more correct") case folding logic,
and reverting will just make other things break.

The correct solution is to not do case folding in filesystems, but
sadly, people seem to never really understand that.  People still see it
as a feature, not a bug.

Reported-by: Qi Han <hanqi@vivo.com>
Link: https://bugzilla.kernel.org/show_bug.cgi?id=219586
Cc: Gabriel Krisman Bertazi <krisman@suse.de>
Requested-by: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/unicode/mkutf8data.c
fs/unicode/utf8data.h_shipped