linux-ext4 - Re: [Patch 4/13] Allow regular files to be preallocated on-disk.

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] [day] [month] [year] [list]

Message-ID: <20070804183825.GA11150@thunk.org>
Date:	Sat, 4 Aug 2007 14:38:25 -0400
From:	Theodore Tso <tytso@....edu>
To:	Andreas Dilger <adilger@...sterfs.com>
Cc:	Girish Shilamkar <girish@...sterfs.com>,
	Ext4 Mailing List <linux-ext4@...r.kernel.org>
Subject: Re: [Patch 4/13] Allow regular files to be preallocated on-disk.

On Sat, Aug 04, 2007 at 10:19:43AM -0600, Andreas Dilger wrote:
> On Aug 03, 2007  20:40 -0400, Theodore Tso wrote:
> > I'm also a little concerned this patch doesn't solve the problem where
> > a filesystem that had been previously mounted on an IA64 machine gets
> > connected to an x86 machine and then e2fsck is run.  This patch
> > doesn't make the problem any more worse, and to fix this for real
> > would require stashing the largest blocksize ever used by the
> > filesystem in the superblock, and I'm not entirely convinced it's
> > worth it.
> 
> At worst we get some warnings in that case and the extra blocks beyond
> EOF are removed.

Yep, that's why I said it's probably not worth it to worry about that
case.  It still bothers me a little, but that's the perfectionist in
me struggling to get out.  :-)

							- Ted

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