linux-hardening - Re: [PATCH] printk: add cpu id information to printk() output

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, 18 Sep 2023 11:00:48 +0206
From:   John Ogness <john.ogness@...utronix.de>
To:     Petr Mladek <pmladek@...e.com>,
        Greg KH <gregkh@...uxfoundation.org>
Cc:     Enlin Mu <enlinmu@...il.com>, Enlin Mu <enlin.mu@...look.com>,
        rostedt@...dmis.org, senozhatsky@...omium.org,
        keescook@...omium.org, tony.luck@...el.com, gpiccoli@...lia.com,
        enlin.mu@...soc.com, linux-kernel@...r.kernel.org,
        linux-hardening@...r.kernel.org
Subject: Re: [PATCH] printk: add cpu id information to printk() output

On 2023-09-15, Petr Mladek <pmladek@...e.com> wrote:
> The biggest problem is that it would change the format of the
> ringbuffer so that it would require updating external tools,
> working with crashdump, especially crash but there are also
> alternative python extensions for gdb.

I already have experience updating these external tools. It is
manageable. But I would prefer we had bigger changes to make. Let us not
forget your RFC [0] where you wanted to add similar metadata and
more. We should put all these changes into a single release.

John Ogness

[0] https://lore.kernel.org/lkml/20200923135617.27149-1-pmladek@suse.com