lkml.org 
[lkml]   [2022]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH rcu 2/8] torture: Distinguish kthread stopping and being asked to stop
    Date
    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 | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/kernel/torture.c b/kernel/torture.c
    index ef27a6c824514..f55d803f995d4 100644
    --- a/kernel/torture.c
    +++ b/kernel/torture.c
    @@ -911,7 +911,7 @@ void torture_kthread_stopping(char *title)
    {
    char buf[128];

    - snprintf(buf, sizeof(buf), "Stopping %s", title);
    + snprintf(buf, sizeof(buf), "%s is stopping", title);
    VERBOSE_TOROUT_STRING(buf);
    while (!kthread_should_stop()) {
    torture_shutdown_absorb(title);
    --
    2.31.1.189.g2e36527f23
    \
     
     \ /
      Last update: 2022-02-05 00:54    [W:3.358 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site