Re: drivers/input/keyboard/applespi.c:1833 applespi_drain_writes() warn: mixing irqsave and irq

[Dan Carpenter]

On Mon, Jul 01, 2024 at 10:14:00AM -0700, Dmitry Torokhov wrote:
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1826  static void applespi_drain_writes(struct applespi_data *applespi)
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1827  {
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1828  	unsigned long flags;
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1829  
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1830  	spin_lock_irqsave(&applespi->cmd_msg_lock, flags);
> > 
> > _irqsave() sort of implies that potentially the caller has disabled IRQs,
> > otherwise we would use spin_lock_irq() if we knew they hadn't disabled
> > IRQs.
> > 
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1831  
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1832  	applespi->drain = true;
> > 038b1a05eae666 Ronald Tschalär 2019-07-15 @1833  	wait_event_lock_irq(applespi->drain_complete, !applespi->write_active,
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1834  			    applespi->cmd_msg_lock);
> > 
> > This will renable IRQs briefly and then disable them again.
> > 
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1835  
> > 038b1a05eae666 Ronald Tschalär 2019-07-15  1836  	spin_unlock_irqrestore(&applespi->cmd_msg_lock, flags);
> > 
> > This will set them back to how they were at the start of the function.
> > 
> > The issue is that if the caller really wanted IRQs disabled, then it's
> > not necessarilly a good idea to enable them at all in the
> > wait_event_lock_irq() macro.  I suspect that in real life no callers
> > disable IRQs so it's not an issue.  But anyway, that's what the warning
> > is about.
> 
> applespi_drain_writes() and applespi_drain_reads() are only called from
> the process context with interrupts enabled, so it looks like we should
> simply change spin_lock_irqsave() to spin_lock_irq().
> 
> I am taking patches ;)

Sure.  I can send that.

regards,
dan carpenter