From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Philippe De Muyter <phdm@macqel.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH vfat] IOMEGA network drive compatibility
Date: Sun, 14 Mar 2010 23:52:51 +0900 [thread overview]
Message-ID: <87bperoszg.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20100314141328.GA7712@frolo.macqel> (Philippe De Muyter's message of "Sun, 14 Mar 2010 15:13:29 +0100")
Philippe De Muyter <phdm@macqel.be> writes:
>> Because it's wrong entry as fatfs. In this situation, user needs to
>> repair by tools (e.g. fsck), so it's not responsibility of fs driver.
>
> I know that entries with trailing dots are "invalid" fatfs entries,
> but 1) linux/vfat currently accept such entries silently without truncating
> them and 2) IOMEGA disks present themselves as fatfs disks. Who are we to
> tell the opposite ? And IOMEGA integrated scandisk (accessible via the
> web interface) does not find any error in its filesystem.
You can create many files points to one cluster chain. It is silently
accepted by current fatfs driver. But, it's a broken fs image like this.
>> Now, you try to change that design. So, you need to change/think more
>> high level consistency/design, not just workaround. Otherwise, it'll be
>> unmaintainable/unfixable.
>
> I am sorry but I don't see anything unmaintainable/unfixable in my patch :
> it is very small and localized and it only allows accessing existing
> entries with trailing dots, nothing more.
>
> It does not allow to create "invalid" entries, so it does not change the
> behaviour for "strict" vfat disks, it only introduces a small time penalty
> when a user tries to access a file using a different name that the one stored
> in the directory, which happens very rarely : most linux users use GUI's or
> bash tab-completion to access files, which implies they use the name given by
> the file-system driver, not a variation of it.
>
> Now if we are concerned about "editing" such files by creating a temporary
> file and renaming, we can look at what is needed to make renaming to an
> existing name containing trailing dots succeed. I have not tested that yet.
>
> For the rest, i.e. creating arbitrary names with trailing dots just like
> what IOMEGA drives do, it can be with a mount option, or left as it is
> now : impossible.
I already reported the one of bugs at least, and it seems you already
can't fix it, or just ignored it.
You are always saying "I'm fine with this". But I disagree, and I know
this fs is not only for just desktop users. If this is only for you
usage, I'm sorry, but please apply it yourself.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2010-03-14 14:52 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 ` [PATCH vfat] IOMEGA network drive compatibility Philippe De Muyter
2010-03-14 11:17 ` OGAWA Hirofumi
2010-03-14 14:13 ` Philippe De Muyter
2010-03-14 14:52 ` OGAWA Hirofumi [this message]
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=87bperoszg.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
/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