linux-kernel - Re: Change of behaviour when console=null and ttynull driver is used

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: <CAHk-=wheQYsUiKmJnqR3qGrjjh8z7b2ov4rZzHLHJS+VJT9aLQ@mail.gmail.com>
Date:   Sun, 26 Mar 2023 16:20:16 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Petr Mladek <pmladek@...e.com>
Cc:     Guillermo Rodriguez Garcia <guille.rodriguez@...il.com>,
        linux-kernel@...r.kernel.org,
        Alejandro Vazquez <avazquez.dev@...il.com>,
        sergey.senozhatsky@...il.com, rostedt@...dmis.org,
        shreyasjoshi15@...il.com, Guenter Roeck <linux@...ck-us.net>
Subject: Re: Change of behaviour when console=null and ttynull driver is used

On Fri, Mar 24, 2023 at 8:08 AM Petr Mladek <pmladek@...e.com> wrote:
>
> I need an advice whether to revert the commit 3cffa06aeef7ece30f
> ("printk/console: Allow to disable console output by using
> console="" or console=null").

I think it's too late to revert it by now. It sounds like people who
were affected are either chrome developers that already changed their
setup, or embedded people who similarly have already reacted to it.

This went into 5.11, it's ancient history by now, so reverting it
would likely just cause more issues.

              Linus