linux-ext4 - [Q] ext3 mkfs: zeroing journal blocks

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

Message-ID: <71a0d6ff0905110803t1a6b34ccq91d5494f95fe1f34@mail.gmail.com>
Date:	Mon, 11 May 2009 18:03:13 +0300
From:	Alexander Shishkin <alexander.shishckin@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: [Q] ext3 mkfs: zeroing journal blocks

Hi,

Here's a question regarding ext3, jbd and mkfs. I'm not 100% confident
this is the right
list, got it from MAINTAINERS for ext3 and jbd. Please correct me if
this is wrong.

As far as I could tell from brief looking at jbd code, it seemed to me
that the only thing
that has to be reset during the filesystem creation time is journal
superblock (talking
about the default case when journal resides within an ext3 partition).
However, currently
mke2fs -j would zero every journal block no matter what. So, the
question is: can this
zeroing really be avoided in mkfs?
I tried commenting-out ext2fs_zero_block() in mkjournal_proc() and it
seems to speed
up mkfs a great deal while the kernel is still able to mount the
partition afterwards. Also,
for the sake of experiment, I filled the partition with urandom's
contents before doing
the modified mkfs and it still works. My next step in this direction
would be to go
through jbd code, but before doing that, I thought, I'd ask here.

Please CC me in replies as I'm not (yet) subscribed.

Regards,
-- 
Alex
--
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