diff options
| author |   Steven Rostedt (VMware) <rostedt@goodmis.org> | 2020-05-10 11:35:10 -0400 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2020-05-11 17:00:34 -0400 |
| commit | 8b1fac2e73e84ef0d6391051880a8e1d7044c847 (patch) | |
| tree | d8802615a1e3948b018965c74599492e9c162ead /init | |
| parent | tools/bootconfig: Fix apply_xbc() to return zero on success (diff) | |
| download | wireguard-linux-8b1fac2e73e84ef0d6391051880a8e1d7044c847.tar.xz wireguard-linux-8b1fac2e73e84ef0d6391051880a8e1d7044c847.zip | |
tracing: Wait for preempt irq delay thread to execute
A bug report was posted that running the preempt irq delay module on a slow
machine, and removing it quickly could lead to the thread created by the
modlue to execute after the module is removed, and this could cause the
kernel to crash. The fix for this was to call kthread_stop() after creating
the thread to make sure it finishes before allowing the module to be
removed.
Now this caused the opposite problem on fast machines. What now happens is
the kthread_stop() can cause the kthread never to execute and the test never
to run. To fix this, add a completion and wait for the kthread to execute,
then wait for it to end.
This issue caused the ftracetest selftests to fail on the preemptirq tests.
Link: https://lore.kernel.org/r/20200510114210.15d9e4af@oasis.local.home
Cc: stable@vger.kernel.org
Fixes: d16a8c31077e ("tracing: Wait for preempt irq delay thread to finish")
Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions