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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ren47plwmywfz3wmg2vjprknyfwzt7rkp4nppnqnnw4hqxdjxt@skmmbvfok3wt>
Date: Wed, 17 Sep 2025 14:13:51 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Pavel Machek <pavel@...nel.org>, Tomasz Figa <tfiga@...omium.org>, 
	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Sergey Senozhatsky <senozhatsky@...omium.org>
Subject: Re: [PATCH] PM: dpm: add module param to backtrace all CPUs

On (25/08/20 11:04), Sergey Senozhatsky wrote:
> 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?

Gentle ping.

Rafael, are you OK with dpm_watchdog_all_cpu_backtrace name?

Or maybe we can have a bitmask dmp_watchdog_print_flags and
various bits can control different things to print/do during
panic.  E.g. dmp_watchdog_print_flags=0x1 can backtrace all CPUs,
0x2 can do something else, etc.