diff options
| author | Viresh Kumar <[email protected]> | 2016-06-23 23:23:06 +0530 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2016-06-23 15:18:42 -0700 |
| commit | fe9054155d831fee7a8e737ff3898c4bc2e5fc4d (patch) | |
| tree | 3a150eb86970ac2e7adab18031e0c1bdd51bd191 /tools/perf/scripts/python | |
| parent | e9f80f3363542b645a5ceb0509273eda1d0e4eab (diff) | |
greybus: es2.c: 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 <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions