From: Zenghui Yu <yuzenghui@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [report] WARN_ON_ONCE() was triggered with pseudo NMI enabled
Date: Mon, 30 Jun 2025 13:08:56 +0800 [thread overview]
Message-ID: <a99ef199-ac63-ac32-12fc-353c8d22fc97@huawei.com> (raw)
In-Reply-To: <aF69MAUB84bPX-Sy@willie-the-truck>
On 2025/6/27 23:48, Will Deacon wrote:
> On Wed, Mar 12, 2025 at 05:27:50PM +0800, Zenghui Yu wrote:
> > With pseudo NMI enabled, I can trigger the following splat when running
> > selftests (e.g., arm64/signal/fake_sigreturn_bad_magic, which will issue
> > a BRK instruction).
> >
> > ------------[ cut here ]------------
> > WARNING: CPU: 5 PID: 386876 at ./arch/arm64/include/asm/irqflags.h:34 send_user_sigtrap+0xc8/0xd0
>
> This is fixed by Ada's series:
>
> https://lore.kernel.org/r/20250620211207.773980-1-ada.coupriediaz@arm.com
Thanks for the heads-up!
Zenghui
prev parent reply other threads:[~2025-06-30 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:27 [report] WARN_ON_ONCE() was triggered with pseudo NMI enabled Zenghui Yu
2025-06-27 15:48 ` Will Deacon
2025-06-30 5:08 ` Zenghui Yu [this message]
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=a99ef199-ac63-ac32-12fc-353c8d22fc97@huawei.com \
--to=yuzenghui@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox