From: Will Deacon <will@kernel.org>
To: Zenghui Yu <yuzenghui@huawei.com>
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: Fri, 27 Jun 2025 16:48:00 +0100 [thread overview]
Message-ID: <aF69MAUB84bPX-Sy@willie-the-truck> (raw)
In-Reply-To: <ce10f231-4ecd-cb12-4b5c-1c503d9177da@huawei.com>
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
> CPU: 5 UID: 0 PID: 386876 Comm: fake_sigreturn_ Kdump: loaded Not
> tainted 6.14.0-rc6-00017-g5e35b5d3ce97-dirty
> pstate: 204003c9 (nzCv DAIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> pc : send_user_sigtrap+0xc8/0xd0
> lr : brk_handler+0x3c/0xbc
> sp : ffff8000ade3be00
> pmr: 000000f0
> x29: ffff8000ade3be00 x28: ffff00209777c600 x27: 0000000000000000
> x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000400e30
> x23: ffff800082cb8458 x22: ffff800082cb83c8 x21: 00000000f200029a
> x20: ffff8000ade3beb0 x19: ffff8000ade3beb0 x18: 0000000000000000
> x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
> x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
> x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
> x8 : 0000000000000000 x7 : 0000000000000000 x6 : ffff8000827e6638
> x5 : 0000000000000000 x4 : ffff8000827e6638 x3 : 0000000060000000
> x2 : ffff8000ade3c000 x1 : 0000000000000001 x0 : 00000000000000d0
> Call trace:
> send_user_sigtrap+0xc8/0xd0 (P)
> brk_handler+0x3c/0xbc
> do_debug_exception+0x68/0x110
> el0_dbg+0x28/0xb8
> el0t_64_sync_handler+0x50/0xcc
> el0t_64_sync+0x1ac/0x1b0
> ---[ end trace 0000000000000000 ]---
>
> I use mainline and the kernel is built with defconfig + ARM64_PSEUDO_NMI
> + ARM64_DEBUG_PRIORITY_MASKING.
This is fixed by Ada's series:
https://lore.kernel.org/r/20250620211207.773980-1-ada.coupriediaz@arm.com
Will
next prev parent reply other threads:[~2025-06-27 17:09 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 [this message]
2025-06-30 5:08 ` Zenghui Yu
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=aF69MAUB84bPX-Sy@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=yuzenghui@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox