linux-ext4 - Re: uninit_bg removed from mke2fs.conf

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

Message-ID: <20180929151908.GB2290@thunk.org>
Date:   Sat, 29 Sep 2018 11:19:09 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Xose Vazquez Perez <xose.vazquez@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: uninit_bg removed from mke2fs.conf

On Sat, Sep 29, 2018 at 03:39:06PM +0200, Xose Vazquez Perez wrote:
> 
> It was removed from misc/mke2fs.conf.in in d0b9e0a6aa7d6805338a43b4e372623352d8df09
> 
> Was it intentional?

Yes, metadata_csum's functionality is a superset of uninit_bg with a
different way of checksuming the block group descriptors.  So it's
contradictory to have both metadata_csum and uninit_bg enabled at the
same time.

						- Ted