linux-kernel - Re: [PATCH take 2][RFC] fat: Save FAT root directory timestamps to volume label

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1248691635.4618.43.camel@jorg-desktop>
Date:	Mon, 27 Jul 2009 13:47:15 +0300
From:	Jörg Schummer <ext-jorg.2.schummer@...ia.com>
To:	ext OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH take 2][RFC] fat: Save FAT root directory timestamps to
	volume label

On Sat, 2009-07-25 at 07:48 +0200, ext OGAWA Hirofumi wrote:
> Jorg Schummer <ext-jorg.2.schummer@...ia.com> writes:
> 
> > Standard FAT implementations cannot store any of the FAT root directory's
> > timestamps. This commit adds the mount option 'rootts', which allows saving
> > the FAT root directory timestamps as the timestamps of the FAT volume label
> > directory entry. At least Mac OS X is known to support the same mechanism
> > and interoperate with this commit.

Hi,

I guess I should have explained a bit more:

> Looks like interesting hack. However, personally, I don't think I want
> this, but I guess it can be only me.

If you don't want this functionality to be used, as pointed out before,
"rootts=ignore" is the default.

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.

> Well, so, what is this for? If rootdir doesn't have timestamp, some app
> is not working, or something?

To be honest, the only app which I can think of here is some
backup-script which I wrote many years ago and which has not been in use
anymore for a long time. (Maybe rsync or similar could also fail under
some circumstances? Not sure.)

So some backup / synchronisation apps might not work properly. But who's
going to use FAT for sensitive, i.e. backup-worthy data anyway? The
answer is: People who use the same volume in many different machines,
some of which might be able to speak only FAT. Drawback: Just for these
people this patch might not be useful since none of those FAT machines
(except for the apple and possibly the penguin) support root dir
timestamps anyway. So whatever timestamps are found at backup-time, they
cannot be trusted, because the volume might have been in use by standard
FAT implementations.

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.. ;-)

Regards,
Jörg

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/