From: Philippe De Muyter <phdm@macqel.be>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH vfat] IOMEGA network drive compatibility
Date: Sun, 14 Mar 2010 11:39:24 +0100 [thread overview]
Message-ID: <20100314103924.GA3712@frolo.macqel> (raw)
In-Reply-To: <87wrxg9xri.fsf@devron.myhome.or.jp>
Hello Ogawa,
I changed the subject to make it more explicit.
On Sat, Mar 13, 2010 at 10:06:25PM +0900, OGAWA Hirofumi wrote:
> Philippe De Muyter <phdm@macqel.be> writes:
>
> >> No, this breaks consistency. With this patch, unlink("a."), then
> >> open("a.", O_CREAT) and write(), the result depend on existent
> >> files. This patch is providing two files on one name.
> >
> > To avoid that, we could remember that we have found a filename with a trailing
> > dot (in that directory or in the whole disk), and if that's the case then
> > we are allowed to create filenames with trailing dots.
>
> It sounds like dirty hack, and it would make more complex situations.
> And the user can umount/mount (or reboot, etc.) before open().
You can call that a hack, but it certainly is better than the current situation.
IOMEGA network drive firmware allows to create two files in the same directory
differing only by the trailing dots. Suppose you have in the same directory
a file called "123456789" and a file called "123456789." (same name + a
trailing dot). When afterwards connected via USB to a linux computer,
ls or any GUI equivalent will show you two files, one called "123456789"
and one called "123456789.". If you compare those two files, linux/vfat
will tell you that they are equal, because the vfat driver will wrongly
access twice the same "123456789" file and never the "123456789." file.
-rwxr-xr-x 1 phdm root 1 2009-10-15 23:44 123456789
-rwxr-xr-x 1 phdm root 1 2009-10-15 23:44 123456789.
If you then decide to remove the "123456789." file (the one with the
trailing dot), because it is an useless copy of your "123456789" file,
linux/vfat will silently remove the "123456789" file. Afterwards,
if you're lucky, you'll see ls complain :
ls: cannot access a.: No such file or directory
, but some GUI interfaces won't say anything.
In the listing, ls will show :
-????????? ? ? ? ? ? 123456789.
(The "123456789" does not appear anymore)
but again some GUI won't even show you the name of the "123456789." file
With my proposed patch, at least if getdents tells a user program that
there is a "123456789." entry, further references by open and friends
will access precisely that entry, not another one. That at least needs to
be fixed, without any option that the user should give to mount.
Best regards
Philippe
next prev parent reply other threads:[~2010-03-14 10:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 12:32 [PATCH vfat] allow retrieving entries with trailing dots Philippe De Muyter
2010-03-10 14:44 ` OGAWA Hirofumi
2010-03-10 16:14 ` Philippe De Muyter
2010-03-10 17:16 ` OGAWA Hirofumi
2010-03-10 23:58 ` Philippe De Muyter
2010-03-11 9:26 ` OGAWA Hirofumi
2010-03-11 12:02 ` Philippe De Muyter
2010-03-11 12:41 ` OGAWA Hirofumi
2010-03-13 11:31 ` Philippe De Muyter
2010-03-13 13:06 ` OGAWA Hirofumi
2010-03-14 10:39 ` Philippe De Muyter [this message]
2010-03-14 11:17 ` [PATCH vfat] IOMEGA network drive compatibility OGAWA Hirofumi
2010-03-14 14:13 ` Philippe De Muyter
2010-03-14 14:52 ` 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=20100314103924.GA3712@frolo.macqel \
--to=phdm@macqel.be \
--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
Powered by JetHome