Re: [PATCH v2 2/3] printk: console_flush_one_record() code cleanup
From: John Ogness
Date: Tue Sep 30 2025 - 08:59:05 EST
On 2025-09-27, Andrew Murray <amurray@xxxxxxxxxxxxxxxxxxxx> wrote:
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 060d4919de320fe21fd7aca73ba497e27c4ff334..e2c1cacdb4164489c60fe38f1e2837eb838107d6 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -3193,6 +3194,7 @@ static bool console_flush_one_record(bool do_cond_resched, u64 *next_seq, bool *
> bool any_progress;
> int cookie;
>
> + *any_usable = false;
Since it is expected that @next_seq and @handover are initialized by
their callers (if their callers are interested in the values), then I
would expect @any_usable to be initialized by the
caller. console_flush_one_record() never reads this variable.
> @@ -3280,21 +3284,16 @@ static bool console_flush_one_record(bool do_cond_resched, u64 *next_seq, bool *
> */
> static bool console_flush_all(bool do_cond_resched, u64 *next_seq, bool *handover)
> {
> - bool any_usable = false;
> + bool any_usable;
Since console_flush_all() does read @any_usable, I would expect it to
initialize @any_usable. So I would not remove this definition initialization.
> bool any_progress;
>
> *next_seq = 0;
> *handover = false;
>
> do {
> - any_progress = console_flush_one_record(do_cond_resched, next_seq, handover,
> - &any_usable);
> + any_progress = console_flush_one_record(do_cond_resched, next_seq,
> + handover, &any_usable);
>
Since the second line of the call to console_flush_one_record() already
has a ton of whitespace, I would remove the above blank line.
John