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: <ZqOcuvuZM7_J-6C3@pathway.suse.cz>
Date: Fri, 26 Jul 2024 14:55:22 +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 v3 04/19] printk: nbcon: Clarify rules of the
 owner/waiter matching

On Mon 2024-07-22 19:25:24, John Ogness wrote:
> The functions nbcon_owner_matches() and nbcon_waiter_matches()
> use a minimal set of data to determine if a context matches.
> The existing kerneldoc and comments were not clear enough and
> caused the printk folks to re-prove that the functions are
> indeed reliable in all cases.
> 
> Update and expand the explanations so that it is clear that the
> implementations are sufficient for all cases.
> 
> Signed-off-by: John Ogness <john.ogness@...utronix.de>

Thanks a lot for documenting this!

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

Best Regards,
Petr

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ