[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172441009653.1922898.7572192517928205189.b4-ty@kernel.org>
Date: Fri, 23 Aug 2024 18:02:10 +0100
From: Will Deacon <will@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>,
Douglas Anderson <dianders@...omium.org>
Cc: kernel-team@...roid.com,
Will Deacon <will@...nel.org>,
Yu Zhao <yuzhao@...gle.com>,
Mark Rutland <mark.rutland@....com>,
Misono Tomohiro <misono.tomohiro@...itsu.com>,
Marc Zyngier <maz@...nel.org>,
Sumit Garg <sumit.garg@...aro.org>,
Chen-Yu Tsai <wens@...e.org>,
Daniel Thompson <daniel.thompson@...aro.org>,
Stephen Boyd <swboyd@...omium.org>,
Frederic Weisbecker <frederic@...nel.org>,
"Guilherme G. Piccoli" <gpiccoli@...lia.com>,
James Morse <james.morse@....com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Kees Cook <kees@...nel.org>,
Puranjay Mohan <puranjay@...nel.org>,
Tony Luck <tony.luck@...el.com>,
linux-arm-kernel@...ts.infradead.org,
linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] arm64: smp: smp_send_stop() and crash_smp_send_stop() should try non-NMI first
On Wed, 21 Aug 2024 14:53:57 -0700, Douglas Anderson wrote:
> When testing hard lockup handling on my sc7180-trogdor-lazor device
> with pseudo-NMI enabled, with serial console enabled and with kgdb
> disabled, I found that the stack crawls printed to the serial console
> ended up as a jumbled mess. After rebooting, the pstore-based console
> looked fine though. Also, enabling kgdb to trap the panic made the
> console look fine and avoided the mess.
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: smp: smp_send_stop() and crash_smp_send_stop() should try non-NMI first
https://git.kernel.org/arm64/c/fdfa588124b6
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists