linux-kernel - Re: [RESEND RFC PATCH v3 -next] tty: serial: add panic serial helper

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

Message-ID: <2023053113-surviving-ride-2dd6@gregkh>
Date:   Wed, 31 May 2023 09:05:53 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Hongyu Xie <xiehongyu1@...inos.cn>
Cc:     linux@...linux.org.uk, jirislaby@...nel.org, rdunlap@...radead.org,
        linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
        xy521521@...il.com
Subject: Re: [RESEND RFC PATCH v3 -next] tty: serial: add panic serial helper

On Wed, May 31, 2023 at 03:18:02PM +0800, Hongyu Xie wrote:
> It was inspired by kgdboc.
> 
> This is a debug module that allows you to get all kernel logs
> after panic.
> 
> Normally you need to attach a USB-to-UART tool or enable kdump
> before panic happens to get log from kernel after panic. If you
> didn't do that and kdump is not working, you can't get any log to
> know what happened before panic. If you have a USB-to-UART tool
> and the uart port on your computer is working. This module helps
> you to get all kernel log after panic() is called.
> 
> To use this, see Documentation/dev-tools/panic_serial_helper.rst.
> 
> Tested on arm64 device.
> 
> Signed-off-by: Hongyu Xie <xiehongyu1@...inos.cn>
> ---
> 
> v3:
>  1. modify the document about this module.
>  2. provide case-ignored filter matching.

Why is this a RESEND?

It's a RFC, I can't apply it, as obviously you do not feel like it is
completed.  What needs to be done to make you feel comfortable with it?

thanks,

greg k-h