2022-09-29 3:42 GMT+09:00, Atte Heikkilä <atteh.mailbox@xxxxxxxxx>: > Share config response may contain the share name without casefolding as > it is known to the user space daemon. When it is present, compare it to > the share name the share config request was made with. If they differ, > casefold it and compare again. If they still differ, we have a share > config which is incompatible with the way we do share config caching. > Currently, this is the case if CONFIG_UNICODE is not set, the share > name contains non-ASCII characters, and those non-ASCII characters do > not match those in the share name known to user space. In other words, > when CONFIG_UNICODE is not set, UTF-8 share names now work but are only > case-insensitive in the ASCII range. > > Signed-off-by: Atte Heikkilä <atteh.mailbox@xxxxxxxxx> Acked-by: Namjae Jeon <linkinjeon@xxxxxxxxxx> Thanks for your work!
