mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: 333776@bugs.debian.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bug#333776: linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive
Date: Fri, 28 Oct 2005 17:22:52 +0900	[thread overview]
Message-ID: <20051028082252.GC11045@verge.net.au> (raw)
In-Reply-To: <20051015003549.GB11040@tennyson.dodds.net>

Ogawa-san,

I'm bringing this to you attention because a) I'm not sure who to ask
and b) I'm not sure what the correct behaviour is.

When a vfat filesystem is mounted isocharset=iso8859-1, then the
following works:

touch a.txt
ls A.txt

But when it is mounted isocharset=utf8, then ls complains, file not
found:

touch a.txt
ls A.txt

That is, in utf8, a =! A on vfat, and thus its not case insensitive
as one might expect.

I took a quick look in fs/nls/nls_utf8.c and I see that this is
intentional.

static struct nls_table table = {
        .charset        = "utf8",
        .uni2char       = uni2char,
        .char2uni       = char2uni,
        .charset2lower  = identity,     /* no conversion */
        .charset2upper  = identity,
        .owner          = THIS_MODULE,
};

I guess it is charset2lower or charset2upper that vfat is calling,
which make no conversion, thus leading to the problem I outlined above.

My question is: Is this behaviour correct, or is it a bug?

-- 
Horms

       reply	other threads:[~2005-10-28  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051013165529.GA2472@tennyson.dodds.net>
     [not found] ` <20051014023216.GJ8848@verge.net.au>
     [not found]   ` <20051015003549.GB11040@tennyson.dodds.net>
2005-10-28  8:22     ` Horms [this message]
2005-10-28 14:54       ` OGAWA Hirofumi
2005-10-28 15:07         ` OGAWA Hirofumi
2005-10-29  3:45           ` Simon Horman [Horms]
2005-10-29 14:45         ` Ingo Oeser
2005-10-29 16:28           ` OGAWA Hirofumi
2005-10-29 18:44             ` Anton Altaparmakov
2005-10-29 20:07               ` OGAWA Hirofumi

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=20051028082252.GC11045@verge.net.au \
    --to=horms@verge.net.au \
    --cc=333776@bugs.debian.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    /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®