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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 1 May 2020 10:30:44 +0900 From: Sergey Senozhatsky <sergey.senozhatsky@...il.com> To: Alper Nebi Yasak <alpernebiyasak@...il.com> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Jiri Slaby <jslaby@...e.com>, Petr Mladek <pmladek@...e.com>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, linux-serial@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, Arvind Sankar <nivedita@...m.mit.edu>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Daniel Vetter <daniel.vetter@...ll.ch>, "David S. Miller" <davem@...emloft.net>, Eric Biggers <ebiggers@...gle.com>, Feng Tang <feng.tang@...el.com>, Grzegorz Halat <ghalat@...hat.com>, Lukas Wunner <lukas@...ner.de>, Nicolas Pitre <nico@...xnic.net>, Sam Ravnborg <sam@...nborg.org> Subject: Re: [RFC PATCH v2 0/3] Prefer working VT console over SPCR and device-tree chosen stdout-path On (20/04/30 19:14), Alper Nebi Yasak wrote: > | "console=tty0" | (no console arg) | > ------------------+-----------------------+-----------------------+ > QEMU VM | tty0 -WU (EC p ) | ttyAMA0 -W- (EC a) | > (w/ SPCR) | ttyAMA0 -W- (E a) | | > ------------------+-----------------------+-----------------------+ > Chromebook Plus | tty0 -WU (EC p ) | ttyS2 -W- (EC p a) | > (w/ stdout-path) | | tty0 -WU (E ) | > ------------------+-----------------------+-----------------------+ > Chromebook Plus | tty0 -WU (EC p ) | tty0 -WU (EC p ) | > (w/o either) | | | > ------------------+-----------------------+-----------------------+ > > This patchset tries to ensure that VT is preferred in those conditions > even in the presence of firmware-mandated serial consoles. These should > cleanly apply onto next-20200430. Well, if there is a "mandated console", then why would we prefer any other console? -ss
Powered by blists - more mailing lists