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: <rbap3e2chlgx7zn2uw5fntjfjoqlfdebsautmiaq4oz7y2ecnx@ejmbrvrtbpju>
Date: Wed, 8 Oct 2025 22:10:39 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Dhruva Gole <d-gole@...com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, 
	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: [PATCHv2] PM: dpm: add module param to backtrace all CPUs

On (25/10/08 18:32), Dhruva Gole wrote:
> What I meant really was to consider another path instead of a mod param,
> something like a /sys/kernel/

Modules' params are exposed to sysfs and are writeable.