diff options
| author | 2012-04-18 22:16:48 +0000 | |
|---|---|---|
| committer | 2012-04-23 11:04:28 +1000 | |
| commit | 3027691e58bfb21f6ea2e9f1d225d11b4e2b20e2 (patch) | |
| tree | 4ff705ce7b3b9b51563777b584d90cf4d0b1a348 /tools/perf/scripts/python/check-perf-trace.py | |
| parent | powerpc/eeh: Fix crash caused by null eeh_dev (diff) | |
| download | wireguard-linux-3027691e58bfb21f6ea2e9f1d225d11b4e2b20e2.tar.xz wireguard-linux-3027691e58bfb21f6ea2e9f1d225d11b4e2b20e2.zip | |
powerpc/pmac: Don't add_timer() twice
If the interrupt and the timeout happen roughly at the same
time, we can get into a situation where the timer function
is run while the interrupt has already been processed. In
this case, the timer function might end up doing an add_timer
on an already pending timer, causing a BUG_ON() to trigger.
Instead, just skip the whole timeout operation if we see that
the timer is pending. The spinlock ensures that the only way
that happens is if we already started a new operation and thus
the timeout can be ignored.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions
