| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20111103134056.178ee9e3@barsoom.rdu.redhat.com> Date: Thu, 3 Nov 2011 13:40:56 -0400 From: Jeff Layton <jlayton@...hat.com> To: Anton Altaparmakov <aia21@....ac.uk> Cc: Steve French <sfrench@...ba.org>, linux-cifs@...r.kernel.org, samba-technical@...ts.samba.org, LKML <linux-kernel@...r.kernel.org>, Unix Support <unix-support@....cam.ac.uk> Subject: Re: CIFS: Rename bug on servers not supporting inode numbers On Thu, 3 Nov 2011 15:42:13 +0000 Anton Altaparmakov <aia21@....ac.uk> 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@...hat.com> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists