linux-kernel - Re: [PATCH] kgdbts: Passing ekgdbts to command line causes panic

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: <X/RxPSR3iQRxH+/o@kroah.com>
Date:   Tue, 5 Jan 2021 15:01:33 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Defang Bo <bodefang@....com>
Cc:     jason.wessel@...driver.com, daniel.thompson@...aro.org,
        dianders@...omium.org, arnd@...db.de,
        kgdb-bugreport@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kgdbts: Passing ekgdbts to command line causes panic

On Mon, Dec 28, 2020 at 09:58:58AM +0800, Defang Bo wrote:
> Similar to commit<1bd54d851f50>("kgdboc: Passing ekgdboc to command line causes panic"),

Please wrap your lines, and use the correct way to reference a commit in
a changelog as documented.  It should look like:
	1bd54d851f50 ("kgdboc: Passing ekgdboc to command line causes panic")

> kgdbts_option_setup does not check input argument before passing it to strlen.
> The argument would be a NULL pointer.

What argument?

As others pointed out, your subject line does not make sense, please fix
up.

thanks,

greg k-h