linux-kernel - Re: [RFC PATCH v2] printk: console: Allow each console to have its own loglevel

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: <YouZF7eWCy8Jrc/O@chrisdown.name>
Date:   Mon, 23 May 2022 15:24:23 +0100
From:   Chris Down <chris@...isdown.name>
To:     Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     linux-kernel@...r.kernel.org, Petr Mladek <pmladek@...e.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        John Ogness <john.ogness@...utronix.de>,
        Geert Uytterhoeven <geert@...ux-m68k.org>, kernel-team@...com
Subject: Re: [RFC PATCH v2] printk: console: Allow each console to have its
 own loglevel

Hi Vincent,

Vincent Whitchurch writes:
>I've had to do something similar for my systems, to allow all messages
>to always be logged to the pstore console while still allowing the UART
>console loglevel to be adjusted.  I've been carrying the following
>pstore-specific hack for a while now.  This patch set looks like it will
>be able to solve the problem in a generic way.

Thanks, nice to hear about other usecases :-) Yes, this should allow this 
generically for any console, including pstore.