]> git.baikalelectronics.ru Git - kernel.git/commit
torture: Distinguish kthread stopping and being asked to stop
authorPaul E. McKenney <paulmck@kernel.org>
Thu, 16 Dec 2021 20:23:31 +0000 (12:23 -0800)
committerPaul E. McKenney <paulmck@kernel.org>
Wed, 2 Feb 2022 01:24:38 +0000 (17:24 -0800)
commite41ffbdc968ef2f75eb330b76dc3b1f9a377fc6a
tree1612f5540396d7a3eab13eac735138d61ae78311
parent7904b4b52c6eb3292a97b3ad6c18c5e9ff633613
torture: Distinguish kthread stopping and being asked to stop

Right now, if a given kthread (call it "kthread") realizes that it needs
to stop, "Stopping kthread" is written to the console.  When the cleanup
code decides that it is time to stop that kthread, "Stopping kthread
tasks" is written to the console.  These two events might happen in
either order, especially in the case of time-based torture-test shutdown.

But it is hard to distinguish these, especially for those unfamiliar with
the torture tests.  This commit therefore changes the first case from
"Stopping kthread" to "kthread is stopping" to make things more clear.

Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
kernel/torture.c