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: <alpine.LSU.2.21.2509111549200.29971@pobox.suse.cz>
Date: Thu, 11 Sep 2025 15:50:42 +0200 (CEST)
From: Miroslav Benes <mbenes@...e.cz>
To: Tiezhu Yang <yangtiezhu@...ngson.cn>
cc: Josh Poimboeuf <jpoimboe@...nel.org>, Huacai Chen <chenhuacai@...nel.org>, 
    Xi Zhang <zhangxi@...inos.cn>, live-patching@...r.kernel.org, 
    loongarch@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/2] livepatch: Add config LIVEPATCH_DEBUG to get
 debug information

Hi,

On Tue, 9 Sep 2025, Tiezhu Yang wrote:

> Add config LIVEPATCH_DEBUG and define DEBUG if CONFIG_LIVEPATCH_DEBUG
> is set, then pr_debug() can print a debug level message, it is a easy
> way to get debug information without dynamic debugging.

I do not have a strong opinion but is it really worth it? Configuring 
dynamic debug is not difficult, it is more targetted (you can enable it 
just for a subset of functions in livepatch subsystem) and it can also be 
done on the command line.

Miroslav

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ