-
Steven Rostedt (VMware) authored
Running on a slower machine, it is possible that the preempt delay kernel thread may still be executing if the module was immediately removed after added, and this can cause the kernel to crash as the kernel thread might be executing after its code has been removed. There's no reason that the caller of the code shouldn't just wait for the delay thread to finish, as the thread can also be created by a trigger in the sysfs code, which also has the same issues. Link: http://lore.kernel.org/r/5EA2B0C8.2080706@cn.fujitsu.com Cc: stable@vger.kernel.org Fixes: 79393723 ("lib: Add module for testing preemptoff/irqsoff latency tracers") Reported-by:
Xiao Yang <yangx.jy@cn.fujitsu.com> Reviewed-by:
Xiao Yang <yangx.jy@cn.fujitsu.com> Reviewed-by:
Joel Fernandes <joel@joelfernandes.org> Signed-off-by:
Steven Rostedt (VMware) <rostedt@goodmis.org>
d16a8c31