linux-kernel - Re: multiplexing /dev/console to all console= entries

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: <955a0492-bab0-59d3-d01d-bea096c6e40f@suse.cz>
Date:   Wed, 7 Nov 2018 10:03:08 +0100
From:   Jiri Slaby <jslaby@...e.cz>
To:     Dusty Mabe <dusty@...tymabe.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: multiplexing /dev/console to all console= entries

On 05. 11. 18, 2:45, Dusty Mabe wrote:
> If a patch were submitted to enable this type of behavior would such a
> patch be acceptable? Maybe it could be a compile time option and also
> have a kernel arg option to enable/disable it.

Hi,

it might kill the system on some setups where people specify more serial
(or similarly slow consoles). Output to some console is so slow that the
system does nothing else than writing to the consoles. What might work
as the first step to check it out is adding a flag to the console=
option which would mark a console as a /dev/console device too and
multiplex only those specified by the user. Then let's see how it goes
with userspace logging out in the wild...

thanks,
-- 
js
suse labs