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. > > I was thinking how to fix it, and the only possible way is to write a > > uni_tolower() function which takes one Unicode code point and returns > > lowercase of input's Unicode code point. We cannot do any Unicode > > normalization as VFAT specification does not say anything about it and > > MS reference fastfat.sys implementation does not do it neither. > > > > So, what would be the best option for implementing that function? > > > > unicode_t uni_tolower(unicode_t u); > > > > Could a new fs/unicode code help with it? Or it is too tied with NFD > > normalization and therefore cannot be easily used or extended? > > To be perfect, the table would have to emulate what Windows use. It can > be unicode standard, or something other. Windows FAT32 implementation (fastfat.sys) is opensource. So it should be possible to inspect code and figure out how it is working. I will try to look at it. > And other fs can use different what Windows use. > > So the table would have to be switchable in perfect world (if there is > no consensus to use 1 table). If we use switchable table, I think it > would be better to put in userspace, and loadable like firmware data. > > Well, so then it would not be simple work (especially, to be perfect). Switchable table is not really simple and I think as a first step would be enough to have one (hardcoded) table for UTF-8. Like we have for all other encodings. > Also, not directly same issue though. There is related issue for > case-insensitive. Even if we use some sort of internal wide char > (e.g. in nls, 16bits), dcache is holding name in user's encode > (e.g. utf8). So inefficient to convert cached name to wide char for each > access. Yes, this is truth. But this conversion is already doing exFAT implementation. I think we do not have other choice if we want Windows compatible implementation. > Relatively recent EXT4 case-insensitive may tackled this though, I'm not > checking it yet. > > > New exfat code which is under review and hopefully would be merged, > > contains own unicode upcase table (as defined by exfat specification) so > > as exfat is similar to FAT32, maybe reusing it would be a better option? > > exfat just put a case conversion table in fs. So I don't think it helps > fatfs. exfat has fallback conversion table (hardcoded in driver) which is used when fs itself does not have conversion table. This is mandated by exfat specification. Part of exFAT specification is that default conversion table. I was thinking... as both VFAT and exFAT are MS standard and exFAT is just evolved FAT32 we could use that exFAT default conversion table (which is prevent in that exfat driver). -- Pali Rohár pali.rohar@xxxxxxxxx
