summaryrefslogtreecommitdiffstats
path: root/arch/sparc/include/asm/sigcontext_64.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2024-12-11 23:11:23 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2024-12-11 23:11:23 +0100
commit231825b2e1ff6ba799c5eaf396d3ab2354e37c6b (patch)
tree3e2895327558e6e54572d2ab00828e4c4c4d7eb2 /arch/sparc/include/asm/sigcontext_64.h
parentMerge tag 'vfio-v6.13-rc3' of https://github.com/awilliam/linux-vfio (diff)
downloadlinux-master.tar.xz
linux-master.zip
Revert "unicode: Don't special case ignorable code points"HEADmaster
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>
Diffstat (limited to 'arch/sparc/include/asm/sigcontext_64.h')
0 files changed, 0 insertions, 0 deletions