linux-kernel - Re: [PATCH printk v1 10/13] printk: add kthread console printers

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: <Ygny42nqV+3R5fp9@google.com>
Date:   Mon, 14 Feb 2022 15:12:51 +0900
From:   Sergey Senozhatsky <senozhatsky@...omium.org>
To:     Petr Mladek <pmladek@...e.com>
Cc:     John Ogness <john.ogness@...utronix.de>,
        Hillf Danton <hdanton@...a.com>, linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH printk v1 10/13] printk: add kthread console printers

On (22/02/08 15:53), Petr Mladek wrote:
> My mine concern is that the kthread_worker API still uses an internal
> lock. And it is yet another layer that might be hard to debug when
> printk() does not work.

Isn't this also true for kthreads? Looks like we add "couple of spin_locks"
to the picture - rq, etc. - one way of the other.