On Wed, 24 Apr 2024 15:21:41 +0100, Daniel Thompson wrote:
> Currently, when kdb is compiled with keyboard support, then we will use
> schedule_work() to provoke reset of the keyboard status. Unfortunately
> schedule_work() gets called from the kgdboc post-debug-exception
> handler. That risks deadlock since schedule_work() is not NMI-safe and,
> even on platforms where the NMI is not directly used for debugging, the
> debug trap can have NMI-like behaviour depending on where breakpoints
> are placed.
>
> [...]
Applied, thanks!
[1/1] serial: kgdboc: Fix NMI-safety problems from keyboard reset code
commit: b2aba15ad6f908d1a620fd97f6af5620c3639742
Best regards,
--
Daniel Thompson <daniel.thompson@xxxxxxxxxx>
