Re: [PATCH v2] locking/lockdep: skip irq save/restore in hardirq context in lock_release()
From: Peter Zijlstra
Date: Tue Jun 30 2026 - 06:15:25 EST
On Tue, Jun 30, 2026 at 05:06:50AM +0530, Deepanshu Kartikey wrote:
> lock_release() performs a raw_local_irq_save/restore dance around its
> validation work. While safe in process and softirq context, this is
> dangerous in hardirq context where IRQs must remain disabled for the
> entire duration of the handler.
>
> When lock_release() calls raw_local_irq_restore() inside a hardirq
> handler, it briefly re-enables IRQs,
It does not.