Re: CIFS: Rename bug on servers not supporting inode numbers

[Jeff Layton]

On Thu, 3 Nov 2011 15:42:13 +0000
Anton Altaparmakov <aia21@xxxxxxxxx> wrote:

> Hi,
> 
> I should add that we are using iocharset=utf8 mount option which means that the dcache hash/compare functions done in the cifs module do not work because it uses nls_tolower() and nls_strnicmp() both of which for utf8 NLS in the kernel do not do anything at all and effectively behave case sensitively!
> 
> Thus this bug/problem in all likelyhood only affects utf8 iocharset users on a case-insensitive but case-preserving CIFS server that does not support server inode numbers.
> 
> That probably explains why it has not been noticed before!
> 
> We need utf8 thus we still need to fix this issue.
> 
> Best regards,
> 
> 	Anton
> 

I'm confused...

If the filesystem being served out by the server is using utf8, then
how is it handling the case-insensitivity?

-- 
Jeff Layton <jlayton@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/