Re:APFS is not safe to use with names which have Unicode nor...
by ridiculous_fish on Tuesday June 06, 2017 @12:39PM
(#14498608)
That's fascinating. What happens on lookup if there's two different files with canonically equivalent names?
[ Parent
| on HN ]
Re:APFS is not safe to use with names which have Unicode nor...
by cryptonector on Tuesday June 06, 2017 @12:49PM
(#14498706)
Great question! You can't have two such files!
Say you create a file with a name that has different NFC and NFD forms, and you create it with the NFC form. Then you go try to create it with the NFD form, well, if doing an exclusive create (O_EXCL) then you'll get EEXIST, else you'll open the existing file.
Re:APFS is not safe to use with names which have Unicode nor...
by throwaway2048 on Tuesday June 06, 2017 @03:42PM
(#14500537)
so it infact does do normalization on file create then? How is it managing this without doing so?
Re:APFS is not safe to use with names which have Unicode nor...
by cryptonector on Tuesday June 06, 2017 @04:02PM
(#14500778)
It normalizes on LOOKUP, not create. On create it preserves the original form. Think of this as like case-preserving/case-insensitive behavior, but for form rather than case.