From: Jeff Layton <jlayton@redhat.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
LKML <linux-kernel@vger.kernel.org>,
Unix Support <unix-support@ucs.cam.ac.uk>
Subject: Re: CIFS: Rename bug on servers not supporting inode numbers
Date: Thu, 3 Nov 2011 13:40:56 -0400 [thread overview]
Message-ID: <20111103134056.178ee9e3@barsoom.rdu.redhat.com> (raw)
In-Reply-To: <81357503-810A-477A-A320-D39F2CD69547@cam.ac.uk>
On Thu, 3 Nov 2011 15:42:13 +0000
Anton Altaparmakov <aia21@cam.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@redhat.com>
next prev parent reply other threads:[~2011-11-03 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 15:20 Anton Altaparmakov
2011-11-03 15:42 ` Anton Altaparmakov
2011-11-03 17:40 ` Jeff Layton [this message]
2011-11-03 23:25 ` Anton Altaparmakov
2011-11-03 23:34 ` Steve French
2011-11-03 23:37 ` NamJae Jeon
2011-11-23 10:34 ` NamJae Jeon
2011-11-23 16:31 ` Alan Stern
2011-11-23 17:12 ` Alan Cox
2011-11-23 18:00 ` Amit Sahrawat
2011-11-24 5:08 ` Günter Kukkukk
2011-11-28 7:56 ` Ashish Sangwan
2011-11-03 18:40 ` Shirish Pargaonkar
2011-11-04 11:16 ` Björn JACKE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111103134056.178ee9e3@barsoom.rdu.redhat.com \
--to=jlayton@redhat.com \
--cc=aia21@cam.ac.uk \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=unix-support@ucs.cam.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®