linux-ext4 - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 May 2009 13:44:18 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Andreas Dilger <adilger@....com>
CC:	Alexander Shishkin <alexander.shishckin@...il.com>,
	linux-ext4@...r.kernel.org
Subject: Re: [Q] ext3 mkfs: zeroing journal blocks

Andreas Dilger wrote:

> The reason that the journal is zeroed is because there is some chance
> that old (valid at the time) transaction headers and commit blocks might
> be in the journal and could accidentally be "recovered" and cause bad
> corruption of the filesystem.

But I guess the question is, why isn't a normal internal log zeroed?

If I'm reading it right only external logs get this treatment, and I
think that's what generated the original question from Alexander.

-Eric
--
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