linux-kernel - Re: pstore/ram: printk: NULL characters in pstore ramoops area

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

Message-ID: <202308102013.380EDA684B@keescook>
Date:   Thu, 10 Aug 2023 20:16:40 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Vijay Balakrishna <vijayb@...ux.microsoft.com>
Cc:     Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        John Ogness <john.ogness@...utronix.de>,
        Colin Cross <ccross@...roid.com>,
        Tony Luck <tony.luck@...el.com>,
        Anton Vorontsov <anton@...msg.org>,
        linux-kernel@...r.kernel.org
Subject: Re: pstore/ram: printk: NULL characters in pstore ramoops area

On Thu, Aug 10, 2023 at 05:48:17PM -0700, Vijay Balakrishna wrote:
> On 8/10/23 16:50, Kees Cook wrote:
> > Can you share the .config you're building with? And what are you using
> > to trigger an Oops? I will see if I can reproduce this...
> 
> 
> Config: https://paste.ubuntu.com/p/Vrcsf8Ry9g/
> 
> Just ran plain "sudo reboot" and inspected /var/lib/systemd/pstore/dmesg-ramoops-0 after reboot.

Ah-ha! I have reproduced by reconfiguring my system to use your exact
memory sizes. And I get the unexpected "dmesg-ramoops-0" file too! I
will continue digging...

-- 
Kees Cook