From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Racy NLS behaviour in FAT (and possible other fs)
Date: Tue, 20 Feb 2007 01:55:39 +0900 [thread overview]
Message-ID: <87tzxim6ic.fsf@duaron.myhome.or.jp> (raw)
In-Reply-To: <45D9C80A.2030905@drzeus.cx> (Pierre Ossman's message of "Mon\, 19 Feb 2007 16\:53\:46 +0100")
Pierre Ossman <drzeus-list@drzeus.cx> writes:
> Hi,
Hi,
> I'm experiencing a rather odd behaviour with the character set
> conversion. If I mount a vfat fs with utf8 and then create a file
> with invalid utf-8 sequences, the file will briefly exist with these
> invalid sequences, then quickly convert to a stripped version.
Yes. utf8 support is broken, and it will fail to convert letter case
on many case. And it's why that is not recommended.
> I haven't found an easy way to catch the race, but if I have
> nautilus open it tends to catch it now and then (I get a file name
> with "<?>" replacing each bad byte).
`?' is meaning the character can't be converted.
> The race also seems to corrupt the in-memory state of the fs now and then. I
> managed to create a file where "ls" shows "?" for most fields. Data seemed to
> have made it to disk ok though (fsck didn't complain and a remount showed
> everything as it should be).
It seems readdir() was success, but stat() was failed. And the dosfsck
doesn't check filename correctly.
Those problem seem to be relateing to poor utf8 support...
> Third, there seems to be a problem with not all syscalls being subjected to the
> NLS transformation. Example:
>
> $ echo foo > baråäö.txt
> $ ls
> foo.txt
> $ echo foo > baråäö.txt
> bash: baråäö.txt: File exists
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2007-02-19 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 15:53 Pierre Ossman
2007-02-19 16:55 ` OGAWA Hirofumi [this message]
2007-02-19 17:03 ` Pierre Ossman
2007-02-19 17:32 ` OGAWA Hirofumi
2007-02-20 6:43 ` Pierre Ossman
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=87tzxim6ic.fsf@duaron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=drzeus-list@drzeus.cx \
--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®