linux-kernel - Re: [PATCH] tty: Add NULL TTY driver

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 12 Apr 2019 09:17:28 +0200
From:   "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To:     "Adamski, Krzysztof (Nokia - PL/Wroclaw)" 
        <krzysztof.adamski@...ia.com>
Cc:     Vincent Whitchurch <vincent.whitchurch@...s.com>,
        Greg KH <gregkh@...uxfoundation.org>,
        "jslaby@...e.com" <jslaby@...e.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tty: Add NULL TTY driver

On 11.04.19 15:05, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote:

> There are (embedded) cases where the kernel ring buffer is stored for> log inspection and all the logs that are *not* wanted there (like>
interactive debug logs, some progress bar, etc) are send specifically
to> /dev/console to avoid sending them to normal log store (as they are
only> useful when debugging over console). In non-debug mode
/dev/console> becomes /dev/null to speed things up.
So, in your case, it doesn't need to be an actual tty, any file/chardev
already do it, correct ? But then, why is that new driver needed ?
--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287