linux-ext4 - Re: Ininitial e2fsprogs TODO list (please expand)

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]

Date:	Mon, 21 Apr 2008 09:11:17 -0400
From:	Theodore Tso <tytso@....EDU>
To:	"Jose R. Santos" <jrs@...ibm.com>
Cc:	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: Ininitial e2fsprogs TODO list (please expand)

On Sun, Apr 20, 2008 at 07:47:07PM -0400, Theodore Tso wrote:
> Some of the items marked "DONE" are in my tree and haven't been pushed
> out yet, but I'll make sure that happens by Monday.  Note that I am
> taking the red eye from Sao Paulo tonight, and if all goes well, am
> scheduled to arrive in Boston at 10:15am Eastern.  If the flight gets
> delayed, there is a chance that I may end up being late or missing the
> ext4 call.

Unfortunately, we were delayed in Sao Paulo for over three hours;
something about a problem with one of the fuel pumps....  So I've been
rebooked onto another flight which means I'll be in the air at the
time of the ext4 call.

While I was stuck on the airplane, I spent some time doing more fixups
on the uninit_bg code to make it much cleaner and more robust, and I
also started rototilling the undo_mgr patches.  

In addition to fixing numerous style and usability problems, I also
found the design problem which caused it to be so slow.  It is using
the first blocksize used to write to the device as the tdb_data_size.
For mke2fs, this is 512 bytes, which means that for every single 4k
inode table clock write, *eight* entries were getting made into the
tdb database and the old contents of the filesystem were getting
stored in 512 byte chunks.  No wonder it was so slow!!  I was able to
show significant speedups by forcing the tdb_data_size to be the
filesystem blocksize, and I suspect that for mke2fs, if it is
initializing the inode table, using a tdb_data_size of something like
32k or 64k would be even better.

Unfortunately I haven't made any progress on doing quality checking
the patches in the patch queue, since I found so much new code that
just screamed out for fixing in e2fsprogs.  Eric, if you have time,
could you look through the patch queue and help out with
sanity-checking the patches and making sure the patch descriptions are
suitably well-written without version control logs, XXX FIXME
comments, or other things that would make Linus vomit?  If you could,
I'd really appreciate it.  Thanks!!

	      	 	   	       	   - 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