On Thu, Jul 24 2025 at 15:22, Waiman Long wrote:Sorry for coming to a conclusion early without looking more deeply into the printk code. I do admit that printk() isn't an area that I know enough about.
On 7/24/25 3:07 PM, Pavel Machek wrote:Wrong you are ... :)
This lockdep problem is likely unrelated to the IRQ flag problemThe lockdep warning just means that console_owner_lock is acquired both inSo you suspect problem is in the printk code?
softirq context and in task context with interrupt enabled. That can leads
to deadlock. So the remedy is to always take console_owner_lock with
interrupt disabled, i.e. with
raw_spin_lock_irqsave/raw_spin_lock_irqrestore.
reported in the original email as it shouldn't affect the IRQ flag.