linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörg Schummer" <ext-jorg.2.schummer@nokia.com>
To: ext OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH take 2][RFC] fat: Save FAT root directory timestamps to volume label
Date: Mon, 27 Jul 2009 16:03:05 +0300	[thread overview]
Message-ID: <1248699785.4618.77.camel@jorg-desktop> (raw)
In-Reply-To: <87ljmas5ym.fsf@devron.myhome.or.jp>

On Mon, 2009-07-27 at 13:47 +0200, ext OGAWA Hirofumi wrote:
> Jörg Schummer <ext-jorg.2.schummer@nokia.com> writes:

> > If you don't want this patch.. There's probably good reasons not to take
> > it, especially the amount-of-problem-solving-by-maintenance-cost ratio
> > might be rather low.

> BTW, the patch has several bugs. fat_get_label_entry() doesn't check
> IS_FREE(), is it right? fat_create_label_entry() doesn't initialize all
> timestamp in the case of msdos. spin_lock() usage is wrong. and more...

You got good points there. I'll fix these on the chance that somebody
decides to use it.

> > In summary: If you're not keen on integrating new features which would
> > make Linux look good in the face of shiny Mac OS, there might not be
> > much reason to take it in. Unless we get zillions of people replying now
> > with what wonderful things it would enable them to do.. ;-)
> 
> Yes, we would really want to know whether people want to use this. Is
> there any info from Mac OS people?
> 
> BTW, my thinking is, the option is why default is "rootts=ignore" if
> it's really good?

That's because this feature does not seem to be part of most generally
accepted FAT implementations. So I thought that the default should try
to behave as people would expect FAT to behave: Forget about root dir
timestamps.
On the other hand, except for 'save', none of the options makes 'real'
fs changes, so maybe 'preserve' could be the default. (People who are
used to the 'standard' behaviour should not be harmed by that - once the
bugs are gone, that is..)

> Or 4 rootts=* options is really needed, and what is
> reason? 

I thought 'ignore' should be there in order to provide the
'standard'-FAT behaviour. And 'save' possibly creates a volume label,
which might be not be wanted. But 'load' is not so necessary, indeed.
The behaviour of Mac OS seems to be like 'preserve', btw.

>  Or if it's not good by some reasons, why is it added? ...

The patch was created merely because one guy figured out that FAT can't
save root dir timestamps by default and another guy knew that Mac OS X's
FAT implementation can. So I thought, what the heck, let's enable linux
to do the same thing.

Like mentioned before, this was not created because it would solve many
people's problems. So I seriously do understand if you decide not to
take it in. But still I would appreciate if you could take another look
at my next - hopefully less buggy - version.

Thanks for your comments,
Jörg


--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-07-27 13:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1248274841-3586-1-git-send-email-ext-jorg.2.schummer@nokia.com>
2009-07-24  9:43 ` [PATCH take 2][RFC] fat: Save FAT root directory timestamps to volume label Jorg Schummer
2009-07-25  5:48   ` OGAWA Hirofumi
2009-07-27 10:47     ` Jörg Schummer
2009-07-27 11:47       ` OGAWA Hirofumi
2009-07-27 13:03         ` Jörg Schummer [this message]
2009-07-27 14:56         ` Jörg Schummer
2009-07-27 15:10           ` OGAWA Hirofumi
2009-08-04  8:42         ` Jörg Schummer
2009-08-04 10:32           ` OGAWA Hirofumi
2009-09-08 14:28             ` [PATCH take 3][RFC] " Jörg Schummer
2009-09-08 14:34               ` Jorg Schummer
2009-09-08 15:39                 ` Jamie Lokier
2009-09-09  7:47                   ` Jörg Schummer
2009-09-15 11:03                 ` Jörg Schummer
2009-09-18 11:33                 ` OGAWA Hirofumi
2009-09-18 12:14                   ` jorg
2009-09-19 14:46                     ` 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=1248699785.4618.77.camel@jorg-desktop \
    --to=ext-jorg.2.schummer@nokia.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).