linux-kernel - Re: [BUG v6.0-rc2] lockdep splat on ct_kernel

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, 22 Aug 2022 18:38:36 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Frederic Weisbecker <fweisbec@...il.com>,
        "Paul E. McKenney" <paulmck@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [BUG v6.0-rc2] lockdep splat on ct_kernel_enter()

On Mon, 22 Aug 2022 18:28:50 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Mon, 22 Aug 2022 16:44:04 -0400
> Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > Looks like lockdep and the trace_rcu_dyntick() code is getting out of sync
> > with respect to whether or not interrupts are enabled.  
> 
> This is caused by this commit:
> 
> 172114552701 ("rcu/context-tracking: Move RCU-dynticks internal functions
> to context_tracking")
> 
> The warning happens with the commit, and does not for the commit just
> before it is applied.
> 

Nevermind, I tested the wrong kernel (the grub reboot failed to boot to the
new kernel). But it did give me a different lockdep splat when I tested the
right kernel :-/

I'll investigate some more.

-- Steve