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
| ||
|
Date: Thu, 27 Oct 2022 14:02:26 +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, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH printk v2 36/38] proc: consoles: use console_list_lock for list iteration On Wed 2022-10-19 17:01:58, John Ogness wrote: > The console_lock is used in part to guarantee safe list iteration. > The console_list_lock should be used because list synchronization > repsponsibility will be removed from the console_lock in a later > change. > > Note, the console_lock is still needed to stop console printing. > > Signed-off-by: John Ogness <john.ogness@...utronix.de> Reviewed-by: Petr Mladek <pmladek@...e.com> Best Regards, Petr
Powered by blists - more mailing lists