linux-kernel - Re: test 1: was: Re: A Comparison of printk between upstream and linux-rt-devel

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: <ZsyVXMqM2SK0aYyV@debarbos-thinkpadt14sgen2i.remote.csb>
Date: Mon, 26 Aug 2024 10:46:52 -0400
From: Derek Barbosa <debarbos@...hat.com>
To: Petr Mladek <pmladek@...e.com>
Cc: pmaldek@...e.com, williams@...hat.com, john.ogness@...utronix.de,
	tglx@...utronix.de, linux-rt-users@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: test 1: was: Re: A Comparison of printk between upstream and
 linux-rt-devel

On Mon, Aug 26, 2024 at 04:02:34PM +0200, Petr Mladek wrote:
> > If you have any other questions, please let me know. I would be happy to re-do
> > these tests with different kernels, configs + other variables and controls.
> 
> It might be interesting to redo the 1st test without the crashdump.
> I wonder if console_flush_on_panic() would allow to see the panic
> backtrace with the stock kernel.

Sure. 

I disabled the systemd kdump service unit via systemctl, and performed a reboot
to ensure that the crashkernel would not be armed.

Performing a trial run of console_blast.sh shows results similar to what was
documented previously, with the difference being we don't reboot after the test
is completed and the kernel has effectively "crashed" via the sysrq-trigger.

I have appended the serial console output as an attachment. You will see that we
do not get a final trace printed.

View attachment "console_blast_nocrashdump_output.txt" of type "text/plain" (55179 bytes)