On Mon, Feb 14, 2022 at 11:43:40PM -0600, Bob Pearson wrote: > in the write_unlock_bh() call. This appears to complain if hardirqs > are not enabled on the current cpu. This only happens if > CONFIG_PROVE_LOCKING=y. The trace shows this context is called within a irq disabled spinlock region. Ie this is trying to do spinlock_irqsave() write_lock_bh() write_unlock_bh() spinunlock_irqrestore() Which is illegal locking. Jason
