RE: vfat: Broken case-insensitive support for UTF-8

[David Laight]

From: Pali RohÃr
> Sent: 20 January 2020 11:05
> On Monday 20 January 2020 13:04:42 OGAWA Hirofumi wrote:
> > Pali RohÃr <pali.rohar@xxxxxxxxx> writes:
> >
> > > Which means that fat_name_match(), vfat_hashi() and vfat_cmpi() are
> > > broken for vfat in UTF-8 mode.
> >
> > Right. It is a known issue.
> 
> Could be this issue better documented? E.g. in mount(8) manpage where
> are written mount options for vfat? I think that people should be aware
> of this issue when they use "utf8=1" mount option.

What happens if the filesystem has filenames that invalid UTF8 sequences
or multiple filenames that decode from UTF8 to the same 'wchar' value.
Never mind ones that are just case-differences for the same filename.

UTF8 is just so broken it should never have been allowed to become
a standard.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)