linux-kernel - Re: design: was: 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: <Ysv4t6ofeq6tL7Oj@google.com>
Date:   Mon, 11 Jul 2022 19:17:27 +0900
From:   Sergey Senozhatsky <senozhatsky@...omium.org>
To:     Petr Mladek <pmladek@...e.com>
Cc:     John Ogness <john.ogness@...utronix.de>,
        Chris Down <chris@...isdown.name>,
        linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>, kernel-team@...com
Subject: Re: design: was: Re: [RFC PATCH v2] printk: console: Allow each
 console to have its own loglevel

On (22/07/11 10:32), Petr Mladek wrote:
> On Fri 2022-07-08 21:10:35, John Ogness wrote:
> > On 2022-07-08, Petr Mladek <pmladek@...e.com> wrote:
> > > The console-specific loglevel might be set by:
> > >
> > >   + "console=device,options/loglevel" kernel parameter at boot time
> > 
> > I ask if we avoid the use of "/loglevel" and instead use a generic
> > scheme of:
> > 
> > console=device,option,option,option
> > 
> > Of course, it would mean that the type of option would need to be
> > specified. Something like:
> > 
> > console=ttyS0,115200n8,loglevel=3
> 
> I like this. It is longer but it makes the meaning very obvious.

Looks beautiful.