linux-kernel - [RFC} Commit 8a99b6833c88 Moves Important Real-time Settings To DebugFS

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

Message-ID: <9e6a7216-9cb9-cba4-f150-1a0eaf56353c@canonical.com>
Date:   Thu, 18 Aug 2022 15:53:28 -0400
From:   Joseph Salisbury <joseph.salisbury@...onical.com>
To:     linux-rt-users@...r.kernel.org, williams@...hat.com,
        bigeasy@...utronix.de
Cc:     peterz@...radead.org, valentin.schneider@....com,
        linux-kernel@...r.kernel.org
Subject: [RFC} Commit 8a99b6833c88 Moves Important Real-time Settings To
 DebugFS

Hello,

Some Ubuntu users are using the tuned package with a 5.15.x based 
real-time kernel.  Tuned adjusts various sysctl options based on a 
specified profile.  This userspace package has stopped working > 5.13 
due to the following commit:

8a99b6833c88 "(sched: Move SCHED_DEBUG sysctl to debugfs)"

This commit moved some important real-time sysctl knobs to debugfs in 
5.13-rc1.  It also appears some of the sysctl options were not moved, 
sched_min_granularity_ns, for example.

I was hoping to get some feedback on how to approach this.  Would 
upstream real-time consider accepting a patch to the 5.15 real-time 
patch set that reverts this commit?  Or a new patch that adds the sysctl 
settings back?  Any other ideas or feedback would be appreciated!

Thanks in advance,

Joe