linux-kernel - Re: [PATCHv2] 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4dsz6s3zfwvfz5iv2labiycqeuu6klry2af4sgzuykpxbzwopg@lulgn7ubg2vu>
Date: Wed, 8 Oct 2025 22:13:14 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Dhruva Gole <d-gole@...com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, 
	"Rafael J. Wysocki" <rafael@...nel.org>, Pavel Machek <pavel@...nel.org>, 
	Tomasz Figa <tfiga@...omium.org>, linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2] PM: dpm: add module param to backtrace all CPUs

On (25/10/08 15:44), Dhruva Gole wrote:
[..]
> >  		dev_emerg(wd->dev, "**** DPM device timeout ****\n");
> >  		show_stack(wd->tsk, NULL, KERN_EMERG);
> > +		if (dpm_watchdog_all_cpu_backtrace)
> > +			trigger_allbutcpu_cpu_backtrace(this_cpu);
> 
> IMO it would be useful to check the ret val of this as well, I mean just
> incase this silently returns false it maybe confusing to figure out what
> hapenned in the system inspite of setting the mod param.

Honestly, I haven't seen a system that constantly modifies
its modules' params at runtime.  It's usually a pretty static
configuration, so I'm not sure if this will address any real
world problem.