linux-kernel - Re: [PATCH printk v4 05/17] printk: nbcon: Init @nbcon

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Zs3Gj-o5_23FMukQ@pathway.suse.cz>
Date: Tue, 27 Aug 2024 14:29:03 +0200
From: Petr Mladek <pmladek@...e.com>
To: John Ogness <john.ogness@...utronix.de>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH printk v4 05/17] printk: nbcon: Init @nbcon_seq to
 highest possible

On Tue 2024-08-27 06:49:21, John Ogness wrote:
> When initializing an nbcon console, have nbcon_alloc() set
> @nbcon_seq to the highest possible sequence number. For all
> practical purposes, this will guarantee that the console
> will have nothing to print until later when @nbcon_seq is
> set to the proper initial printing value.
> 
> This will be particularly important once kthread printing is
> introduced because nbcon_alloc() can create/start the kthread
> before the desired initial sequence number is known.
> 
> Signed-off-by: John Ogness <john.ogness@...utronix.de>

Reviewed-by: Petr Mladek <pmladek@...e.com>

Best Regards,
Petr