linux-ext4 - e2fsprogs-1.39-tyt3

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 for Android: free password hash cracker in your pocket

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

Message-Id: <E1HiXhp-0002Fi-Mm@candygram.thunk.org>
Date:	Mon, 30 Apr 2007 11:22:25 -0400
From:	"Theodore Ts'o" <tytso@....edu>
To:	linux-ext4@...r.kernel.org
Subject: e2fsprogs-1.39-tyt3

Per last week's conference call, I've included an update of the
e2fsprogs patchset to support extents.   It still needs more work before
it can be folded into mainline, but I'm including them so that people
can see which way I'm headed, and because debugfs has been enhaced to
show extents, which can be useful for developers.

One concern I still have is the fact that we're exposing a lot of
interfaces in libext2fs.so which are very specifically tied to the
current 48-bit physical/32-bit logical on-disk extent data structure.
If/when we add support for the 64/64-bit extent data structure, and some
kind of compressed/bit-packed extent format, those interfaces will have
to be extended.

Another problem is that while external extent blocks are getting byte
swapped, there is no byte swapping going on for the extents stored in
the inode.  I haven't tried it on a big endian system, such as Power
machine, but I'm pretty sure it's going to blow up spectacularly.

The patches can be found at:

ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs-interim/e2fsprogs-1.39-tyt3

						- 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