From: Thomas Gleixner <tglx@linutronix.de>
To: paulmck@kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, kernel-team@meta.com
Subject: Re: [BUG] Lockdep warning from "genirq/cpuhotplug: Convert to lock guards"
Date: Fri, 09 May 2025 08:12:01 +0200 [thread overview]
Message-ID: <87plgil3da.ffs@tglx> (raw)
In-Reply-To: <a6f59b64-1604-4186-8a75-8ad776974a65@paulmck-laptop>
On Thu, May 08 2025 at 15:29, Paul E. McKenney wrote:
> Testing next-20250508 with lockdep enabled got a splat that is shown in
> all its glory below. Reverting this commit makes the problem go away:
>
> 88a4df117ad6 ("genirq/cpuhotplug: Convert to lock guards")
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=irq/core
next prev parent reply other threads:[~2025-05-09 6:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 22:29 [BUG] Lockdep warning from "genirq/cpuhotplug: Convert to lock guards" Paul E. McKenney
2025-05-09 6:12 ` Thomas Gleixner [this message]
2025-05-09 14:29 ` Paul E. McKenney
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=87plgil3da.ffs@tglx \
--to=tglx@linutronix.de \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox