Re: [PATCHSET 0/3] xfs: fix ascii-ci problems with userspace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 4, 2023 at 10:17 AM Darrick J. Wong <djwong@xxxxxxxxxx> wrote:
>
> My finger slipped and I accidentally added you to the To: list on this
> new series.  This series needs to go through review on linux-xfs; when
> this is ready to go I (or Dave) will send you a pull request.
>
> Sorry about the noise.

No, it's good. See my rant emails.

Case insensitivity is a subject near and dear to my heart.

And when I say "near and dear to my heart", I obviously mean "I
despise it, and I have spent _decades_ ranting against it and trying
to explain why it's a problem".

I've ranted against it before, but it's been probably a decade since I
needed to. I was hoping this was long behind us.

I'm surprised people still think it's even acceptable.

FAT isn't known for being a great filesystem. HFS+ was garbage, but
even Apple eventually got the message and tried to make APFS better.
I'm not sure Apple succeeded (maybe the case insensitivity is still
the default on OS X, but apparently at least iOS got the message).

Every single case-insensitive filesystem in the world HAS BEEN CRAP.
Please. Learn from literally decades of reality, and stop doing it.

And if you have to do it for some legacy reason, at least understand
the problems with it. Understand that you DO NOT KNOW what the user
space locale is.

Limiting yourself to US-ASCII is at least technically valid. Because
EBCDIC isn't worth worrying about.  But when the high bit is set, you
had better not touch it, or you need to limit it spectacularly.

                   Linus




[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux