[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220620232838.GZ1790663@paulmck-ThinkPad-P17-Gen-1>
Date: Mon, 20 Jun 2022 16:28:38 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: John Ogness <john.ogness@...utronix.de>
Cc: rcu@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...com, rostedt@...dmis.org
Subject: Re: [PATCH rcu 11/12] torture: Flush printk() buffers before
powering off
On Tue, Jun 21, 2022 at 01:29:04AM +0206, John Ogness wrote:
> On 2022-06-20, "Paul E. McKenney" <paulmck@...nel.org> wrote:
> > The rcutorture test suite produces quite a bit of console output
> > at the end of a test. This means that the new printk() kthreads
> > are likely to be in the process of flushing output at the time of
> > the torture_shutdown() function's call to kernel_power_off().
> >
> > This commit therefore invokes pr_flush(1000, true) to flush this
> > pending console output before invoking kernel_power_off().
> >
> > Fixes: 8e274732115f ("printk: extend console_lock for per-console locking")
> > Cc: John Ogness <john.ogness@...utronix.de>
> > Signed-off-by: Paul E. McKenney <paulmck@...nel.org>
>
> Reviewed-by: John Ogness <john.ogness@...utronix.de>
Thank you, John!
But given Petr's and your recent changes that are now in mainline, is
this still really needed? (Tests now pass without it, though tests can
of course be misleading.)
Thanx, Paul
Powered by blists - more mailing lists