greybus: uart: don't use spin_lock_irq()
commite9f80f3363542b645a5ceb0509273eda1d0e4eab
authorViresh Kumar <viresh.kumar@linaro.org>
Thu, 23 Jun 2016 17:53:06 +0000 (23 23:23 +0530)
committerGreg Kroah-Hartman <gregkh@google.com>
Thu, 23 Jun 2016 22:17:46 +0000 (23 15:17 -0700)
tree4d5f2f0d84534253578697d0101d9ab38ecb67e2
parent19cdabcf0ba92ddd87bdb86f8e3ceaae2dd6f8bb
greybus: uart: don't use spin_lock_irq()

spin_[un]lock_irq() routines should be used carefully as they things can
go wrong, if they are mixed with spin_lock_irqsave() or other variants.

The main problem is that spin_[un]lock_irq() routines doesn't check if
the IRQs are already disabled/enabled on the local CPU and so
spin_unlock_irq() will forcefully enable interrupts for example.

This may not work well, if some other code was relying on interrupts
being disabled.

Use spin_lock_irqsave() and spin_unlock_restore() instead.

This patch doesn't claim that it fixes the JIRA completely, but
the issue was harder to reproduce for some iterations after this, which
was quite easy to reproduce earlier on.

Tested on EVT 2.0 with lots of debug patches to kernel and greybus.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
drivers/staging/greybus/uart.c