diff options
| author | Leonid Shatz <leonid.shatz@ravellosystems.com> | 2013-02-04 14:33:37 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-02-28 06:32:23 -0800 |
| commit | bdc82b1e7a4dfc5b287d3f52e173ba8e0183be15 (patch) | |
| tree | 46d62a270a595557a408ec2f4262b733eb0bed44 /sound/pci/ali5451/ali5451.c | |
| parent | c56dec21a605c9cad4e37492ca292f114d2aad34 (diff) | |
| download | kernel_samsung_smdk4412-bdc82b1e7a4dfc5b287d3f52e173ba8e0183be15.zip kernel_samsung_smdk4412-bdc82b1e7a4dfc5b287d3f52e173ba8e0183be15.tar.gz kernel_samsung_smdk4412-bdc82b1e7a4dfc5b287d3f52e173ba8e0183be15.tar.bz2 | |
hrtimer: Prevent hrtimer_enqueue_reprogram race
commit b22affe0aef429d657bc6505aacb1c569340ddd2 upstream.
hrtimer_enqueue_reprogram contains a race which could result in
timer.base switch during unlock/lock sequence.
hrtimer_enqueue_reprogram is releasing the lock protecting the timer
base for calling raise_softirq_irqsoff() due to a lock ordering issue
versus rq->lock.
If during that time another CPU calls __hrtimer_start_range_ns() on
the same hrtimer, the timer base might switch, before the current CPU
can lock base->lock again and therefor the unlock_timer_base() call
will unlock the wrong lock.
[ tglx: Added comment and massaged changelog ]
Signed-off-by: Leonid Shatz <leonid.shatz@ravellosystems.com>
Signed-off-by: Izik Eidus <izik.eidus@ravellosystems.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Link: http://lkml.kernel.org/r/1359981217-389-1-git-send-email-izik.eidus@ravellosystems.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'sound/pci/ali5451/ali5451.c')
0 files changed, 0 insertions, 0 deletions