linux-kernel - Re: Automating console

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]

Date: Mon, 19 Feb 2024 18:57:23 +0106
From: John Ogness <john.ogness@...utronix.de>
To: "John B. Wyatt IV" <jwyatt@...hat.com>
Cc: Petr Mladek <pmladek@...e.com>, Clark Williams <williams@...hat.com>,
 Juri Lelli <jlelli@...hat.com>, Derek Barbosa <debarbos@...hat.com>, Bruno
 Goncalves <bgoncalv@...hat.com>, "John B. Wyatt IV"
 <sageofredondo@...il.com>, LKML <linux-kernel@...r.kernel.org>,
 linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: Automating console_blast.sh

On 2024-02-19, "John B. Wyatt IV" <jwyatt@...hat.com> wrote:
> I am investigating if we can automate, and, possibly add
> console_blash.sh [1] to our test suite here at Red Hat.

It is called "console_blast.sh". ;-)

> At Red Hat we use SSH to manage our test boxes. On an off-list email
> you wrote that 'Only the UART should be used as a console'. I took
> this as no ssh session should be used from the boot up until the
> crash, but I should have confirmed this. Is this correct?

SSH is fine. SSH sessions are not consoles. Consoles are specified with
the console= or netconsole= boot argument and receive the kernel
messages automatically from the kernel.

> The license for our test suite is GPL v3 [2]. May we have your
> permission to license it under that or permissive?

Yes, GPL v3 is OK.

> [1] https://lore.kernel.org/linux-rt-users/ZcQjxa4UA6hzXHnU@thinkpad2021/
>
> [2] https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/tree/main/rt-tests

John