linux-kernel - Re: [PATCH 2/2] lockdep: Remove BROKEN flag of LOCKDEP

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

Message-ID: <20171018101208.jybvncw6odabdooj@gmail.com>
Date:   Wed, 18 Oct 2017 12:12:08 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Byungchul Park <byungchul.park@....com>
Cc:     peterz@...radead.org, tglx@...utronix.de,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        kernel-team@....com
Subject: Re: [PATCH 2/2] lockdep: Remove BROKEN flag of LOCKDEP_CROSSRELEASE


* Byungchul Park <byungchul.park@....com> wrote:

> Now the performance regression was fixed, re-enable LOCKDEP_CROSSRELEASE
> and LOCKDEP_COMPLETIONS.

Please write out CONFIG_ variables, i.e. CONFIG_LOCKDEP_CROSSRELEASE, etc. - to 
make it all more apparent to the reader that it's all Kconfig space changes.

Thanks,

	Ingo