linux-ext4 - Re: [PATCH 0/5][64-BIT] Miscellaneous e2fsprogs 64-bit patches

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: <20090416003146.GH21586@mit.edu>
Date:	Wed, 15 Apr 2009 20:31:46 -0400
From:	Theodore Tso <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Valerie Aurora Henson <vaurora@...hat.com>,
	Nick Dokos <nicholas.dokos@...com>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 0/5][64-BIT] Miscellaneous e2fsprogs 64-bit patches -
	description

On Wed, Apr 15, 2009 at 02:56:15PM -0500, Eric Sandeen wrote:
> Valerie Aurora Henson wrote:
> >> Or I can forego the compression and try to save to a file: it's sparse
> >> (I only used 7GiB before it failed), but its nominal size exceeded the
> >> maximum file size limit on ext4, at which point I start getting lseek
> >> failures.
> 
> We really need some e2image format which encodes the sparseness, I think...

On my two do list for when I have copies amounts of free time is to
take the qemu image format code, and retrofit it into the I/O manager
code, and then teach e2image to use it, and then teach e2fsck,
debugfs, dumpe2fs, to be able to specify that arbitrary I/O managers
by name.  That would allow dumpe2fs, debugfs, e2fsck, etc., to operate
on an qemu-img file, where e2image would have a new option to create a
meta-data only qemu-img format file.

Now, if I only had a minion at hand to carry out my evil plans.   :-)

     	       	     	       	       	     - 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