linux-kernel - Re: [PATCH -next] lockdep: skip debugobjects for lock

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: <59ac7210-03f5-99db-8ffd-47dbfc307709@lca.pw>
Date:   Sun, 3 Mar 2019 22:06:27 -0500
From:   Qian Cai <cai@....pw>
To:     Bart Van Assche <bvanassche@....org>, peterz@...radead.org,
        mingo@...hat.com, will.deacon@....com
Cc:     longman@...hat.com, tglx@...utronix.de,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] lockdep: skip debugobjects for lock_classes[] init



On 3/3/19 1:19 PM, Bart Van Assche wrote:
> [PATCH] locking/lockdep: Only call init_rcu_head() after RCU has been
>  initialized
> 
> init_data_structures_once() is called for the first time before RCU has
> been initialized. Make sure that init_rcu_head() is called before the
> RCU head is used and after RCU has been initialized.
> 
> Signed-off-by: Bart Van Assche <bvanassche@....org>

I like your approach more.

Tested-by: Qian Cai <cai@....pw>