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
| ||
|
Message-ID: <ccf51347-d00e-43cf-9d6f-1a3190a87e14@roeck-us.net> Date: Sun, 26 Mar 2023 20:38:31 -0700 From: Guenter Roeck <linux@...ck-us.net> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Petr Mladek <pmladek@...e.com>, 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 Subject: Re: Change of behaviour when console=null and ttynull driver is used On Sun, Mar 26, 2023 at 04:20:16PM -0700, Linus Torvalds wrote: > 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. > Autually, our (non-)solution was to revert the patches in question in all ChromeOS branches. > This went into 5.11, it's ancient history by now, so reverting it > would likely just cause more issues. > Agreed. Maybe we'll find a better solution at some point, but for now we'll just keep the reverts in ChromeOS. Guenter
Powered by blists - more mailing lists