From: Waiman Long <longman@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH] arm64/entry: Don't disable preemption in debug_exception_enter() with RT kernel
Date: Wed, 20 May 2026 17:01:00 -0400 [thread overview]
Message-ID: <a5251664-2c15-4a8e-906b-d204e10c38be@redhat.com> (raw)
In-Reply-To: <20260520061920.XCqBHe0x@linutronix.de>
On 5/20/26 2:19 AM, Sebastian Andrzej Siewior wrote:
> On 2026-05-19 18:25:24 [-0400], Waiman Long wrote:
>> Commit d8bb6718c4db ("arm64: Make debug exception handlers visible from
>> RCU") introduces debug_exception_enter() and debug_exception_exit()
>> where preemption is explicitly disabled. With a PREEMPT_RT debug kernel,
>> the following bug report can happen.
> …
>
> What kernel is this? I have backport (which is being tested) for v6.6
> and v6.12, the patches are from v6.17-rc1.
The kernel backtrace is produced using the latest v7.1-rc4 kernel. There
are a number of changes to the debug_exception_enter() and
debug_exception_exit() functions over the years, but the preemption
disable code remains since its introduction in v5.3.
BTW, what v6.17-rc1 patches are you talking about?
-Longman
next prev parent reply other threads:[~2026-05-20 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 22:25 Waiman Long
2026-05-20 0:23 ` Luis Claudio R. Goncalves
2026-05-20 6:19 ` Sebastian Andrzej Siewior
2026-05-20 11:23 ` Luis Claudio R. Goncalves
2026-05-20 21:01 ` Waiman Long [this message]
2026-05-28 14:51 ` Sebastian Andrzej Siewior
2026-05-28 15:35 ` Sebastian Andrzej Siewior
2026-05-30 0:51 ` Luis Claudio R. Goncalves
2026-06-15 17:21 ` Sebastian Andrzej Siewior
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=a5251664-2c15-4a8e-906b-d204e10c38be@redhat.com \
--to=longman@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=clrkwllms@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®