linux-kernel - [PATCH locking/csd-lock] make CSD lock debug tunables writable in /sys

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>] [day] [month] [year] [list]

Message-ID: <1bb69e82-af7c-4805-bd93-11c454261a47@paulmck-laptop>
Date: Thu, 12 Dec 2024 10:58:32 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: neeraj.upadhyay@...nel.org, tglx@...utronix.de
Cc: linux-kernel@...r.kernel.org, riel@...riel.com
Subject: [PATCH locking/csd-lock] make CSD lock debug tunables writable in
 /sys

Currently the CSD lock tunables can only be set at boot time in the
kernel commandline, but the way these variables are used means there
is really no reason not to tune them at runtime through /sys.

Make the CSD lock debug tunables tunable through /sys.

Signed-off-by: Rik van Riel <riel@...riel.com>
Signed-off-by: Paul E. McKenney <paulmck@...nel.org>

diff --git a/kernel/smp.c b/kernel/smp.c
index 27dc31a146a35..a33e575f97ab9 100644
--- a/kernel/smp.c
+++ b/kernel/smp.c
@@ -170,9 +170,9 @@ static DEFINE_PER_CPU(smp_call_func_t, cur_csd_func);
 static DEFINE_PER_CPU(void *, cur_csd_info);

 static ulong csd_lock_timeout = 5000;  /* CSD lock timeout in milliseconds. */
-module_param(csd_lock_timeout, ulong, 0444);
+module_param(csd_lock_timeout, ulong, 0644);
 static int panic_on_ipistall;  /* CSD panic timeout in milliseconds, 300000 for five minutes. */
-module_param(panic_on_ipistall, int, 0444);
+module_param(panic_on_ipistall, int, 0644);

 static atomic_t csd_bug_count = ATOMIC_INIT(0);