From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [BUG v6.0-rc2] lockdep splat on ct_kernel_enter()
Date: Mon, 22 Aug 2022 18:38:36 -0400 [thread overview]
Message-ID: <20220822183836.6b80976f@gandalf.local.home> (raw)
In-Reply-To: <20220822182850.32f91017@gandalf.local.home>
On Mon, 22 Aug 2022 18:28:50 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 22 Aug 2022 16:44:04 -0400
> Steven Rostedt <rostedt@goodmis.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
next prev parent reply other threads:[~2022-08-22 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 20:44 [BUG v6.0-rc2] lockdep splat on ct_kernel_enter() Steven Rostedt
2022-08-22 22:28 ` Steven Rostedt
2022-08-22 22:38 ` Steven Rostedt [this message]
2022-08-23 0:48 ` Steven Rostedt
2022-08-23 1:40 ` Steven Rostedt
2022-08-23 2:01 ` Steven Rostedt
2022-08-23 2:36 ` Paul E. McKenney
2023-03-01 12:37 ` Cheng-Jui Wang (王正睿)
2023-03-01 12:52 ` gregkh
2023-03-02 3:42 ` Cheng-Jui Wang (王正睿)
2023-03-02 6:42 ` gregkh
2023-03-01 14:14 ` Frederic Weisbecker
2023-03-01 20:15 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220822183836.6b80976f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.