[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X7fRpVezPnh2uCVc@alley>
Date: Fri, 20 Nov 2020 15:24:37 +0100
From: Petr Mladek <pmladek@...e.com>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Guenter Roeck <linux@...ck-us.net>,
Shreyas Joshi <shreyas.joshi@...mp.com>,
shreyasjoshi15@...il.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] printk/console: Use ttynull when no console is
available or wanted
On Wed 2020-11-11 14:54:48, Petr Mladek wrote:
> This is another attempt to solve regression caused by the commit
> 48021f98130880dd74 ("printk: handle blank console arguments passed in.").
>
> It prevented a crash caused by empty console= parameter. But it caused
> performance problems on Chromebooks because they use it to disable
> all consoles, see
> see https://lore.kernel.org/r/20201006025935.GA597@jagdpanzerIV.localdomain
>
> Solve both problems by using ttynull console driver that was crated
> exactly for this purpose.
>
> The 1st patch should prevent the crash for any invalid console name.
>
> The 2nd patch allows to used the ttynull driver also with the widely
> used console= and console=null parameters.
>
> Best Regards,
> Petr
>
> Petr Mladek (2):
> init/console: Use ttynull as a fallback when there is no console
> printk/console: Allow to disable console output by using console="" or
> console=null
The patchset has been committed into printk/linux.git, branch
for-5.11-null-console.
Best Regards,
Petr
Powered by blists - more mailing lists