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] [day] [month] [year] [list]

Message-ID: <81094a73-c277-99cd-190b-37c25db5f7ab@dustymabe.com>
Date:   Wed, 7 Nov 2018 16:34:05 -0500
From:   Dusty Mabe <dusty@...tymabe.com>
To:     Jiri Slaby <jslaby@...e.cz>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: multiplexing /dev/console to all console= entries



On 11/7/18 4:03 AM, Jiri Slaby wrote:
> 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 Jiri!

I think that seems reasonable. Do you have a good idea of what you'd like it
to look like? Some options

- console=ttyS0,primary
- console=ttyS0,mux
- console=ttyS0+
- consolex=ttyS0

These are ideas. Bad ones, probably. But just throwing out ideas. 

Dusty