From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org,
Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
Ritesh Harjani <ritesh.list@gmail.com>,
"Mukesh Kumar Chaurasiya (IBM)" <mkchauras@gmail.com>
Subject: Re: 7.3.0-rc4: DEBUG_LOCKS_WARN_ON(lockdep_hardirq_context())
Date: Tue, 22 Sep 2026 17:19:46 +0200 [thread overview]
Message-ID: <20260922151946.4eUhMiz7@linutronix.de> (raw)
In-Reply-To: <d8d9ee29-e871-4657-9951-36a3b2b2ea56@linux.ibm.com>
On 2026-09-22 20:43:14 [+0530], Shrikanth Hegde wrote:
> Hi Sebastian.
Hi Shrikanth,
> What do you mean nothing on recent one? You don't see the lockdep warning?
I do as seen below. I wasn't sure if this new that nobody triggered or
the same thing in different shape (and a new report isn't needed).
…
> IIRC, it is tricky to fix since softreplay is a unique thing on its own
> and tracking right context gets tricky.
>
> Mukesh had spent some time on it. Lets wait to hear from him.
>
> Plus we had some more lockdep warnings too. There is effort ongoing to fix
> them. Hopefully soon.
I see. In that case I lay low. Thanks.
Sebastian
next prev parent reply other threads:[~2026-09-22 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 15:06 7.3.0-rc4: DEBUG_LOCKS_WARN_ON(lockdep_hardirq_context()) Sebastian Andrzej Siewior
2026-09-22 15:13 ` Shrikanth Hegde
2026-09-22 15:19 ` Sebastian Andrzej Siewior [this message]
2026-09-23 6:25 ` Mukesh Kumar Chaurasiya
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=20260922151946.4eUhMiz7@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=chleroy@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mchauras@linux.ibm.com \
--cc=mkchauras@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=sshegde@linux.ibm.com \
/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.