diff options
author | Peter Zijlstra <[email protected]> | 2018-05-04 11:11:42 +0200 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2018-05-25 08:03:51 +0200 |
commit | b1f5b378e126133521df668379249fb8265121f1 (patch) | |
tree | ee2ffdde3e7ca65a6090babe51ae1851411e0903 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | bf5015a50f1fdb248b48405b67cae24dc02605d6 (diff) |
kthread: Allow kthread_park() on a parked kthread
The following commit:
85f1abe0019f ("kthread, sched/wait: Fix kthread_parkme() completion issue")
added a WARN() in the case where we call kthread_park() on an already
parked thread, because the old code wasn't doing the right thing there
and it wasn't at all clear that would happen.
It turns out, this does in fact happen, so we have to deal with it.
Instead of potentially returning early, also wait for the completion.
This does however mean we have to use complete_all() and re-initialize
the completion on re-use.
Reported-by: LKP <[email protected]>
Tested-by: Meelis Roos <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: kernel test robot <[email protected]>
Cc: [email protected]
Cc: Thomas Gleixner <[email protected]>
Fixes: 85f1abe0019f ("kthread, sched/wait: Fix kthread_parkme() completion issue")
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions