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]

Message-ID: <71a0d6ff0905120455x291d7280ybe8d1a562987fd1b@mail.gmail.com>
Date:	Tue, 12 May 2009 14:55:10 +0300
From:	Alexander Shishkin <alexander.shishckin@...il.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org
Subject: Re: [Q] ext3 mkfs: zeroing journal blocks

On 11 May 2009 21:44, Eric Sandeen <sandeen@...hat.com> wrote:
> 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.

My concern was basically if it is safe to skip zeroing for internal journal.

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