linux-kernel - Re: [PATCH] PM: dpm: add module param to backtrace all CPUs

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: <afspavnfnnhyttvxmcgdl76jwpawqp7v7g7dd5bnjfc3vv3hg7@g3zey3r3zqc4>
Date: Wed, 20 Aug 2025 11:04:44 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, 
	Pavel Machek <pavel@...nel.org>, Tomasz Figa <tfiga@...omium.org>, linux-pm@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PM: dpm: add module param to backtrace all CPUs

On (25/08/19 21:35), Rafael J. Wysocki wrote:
> On Thu, Jul 31, 2025 at 5:01 AM Sergey Senozhatsky
> <senozhatsky@...omium.org> wrote:
> >
> > Add dpm_all_cpu_backtrace module parameter which controls
> > all CPU backtrace dump before DPM panics the system.
> 
> This is exclusively about the DPM watchdog, so the module parameter
> name should reflect that.

I thought dpm in dpm_all_cpu_backtrace explains that.  Should
I rename it so something like dpm_watchdog_all_cpu_backtrace?
Any better suggestions?

> Also, it is not quite clear which module this is going to belong to,
> so a comment with this information would be helpful.

Ack, I'll add MODULE_PARM_DESC().