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: <CAJZ5v0g-f2dzKJZDZ_fxrDL+JYcF3JxjargBVT3RVcXhVVywjw@mail.gmail.com>
Date: Wed, 8 Oct 2025 15:47:50 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Dhruva Gole <d-gole@...com>, "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 Wed, Oct 8, 2025 at 3:10 PM Sergey Senozhatsky
<senozhatsky@...omium.org> wrote:
>
> 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.

Some of them aren't writable, but this particular one is.