linux-kernel - Re: [RESEND PATCH] sched/syscalls: Allow setting niceness using sched

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

Message-ID: <pOIpWW9nGoJJKFRKRfj0SCJr5LH9bCDGcuNDMSB2Uo1sYLeFJGmJIa6_gvj3UZGH7bpuHut02MEPuEA-mAvBH9fymaf2IELMF_MBFuMWs0s=@pm.me>
Date: Wed, 25 Sep 2024 03:35:01 +0000
From: Michael Pratt <mcpratt@...me>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Ingo Molnar <mingo@...hat.com>, Vincent Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>, linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [RESEND PATCH] sched/syscalls: Allow setting niceness using sched_param struct

Hi Peter,

Have I addressed your concerns?

In my opinion, this is a simple change that adds ABI functionality,
without affecting any other parts of the syscalls involved, whether breaking or non-breaking.

Like I said in previous replies, POSIX doesn't allow passing a negative number
as a successful value, and setting the static priority directly can expose
the scheduler to invalid priority values for CFS policies in later syscalls.

As far as I can see, this is the only way for usage of posix_spawnattr_setschedparam()
to be both compliant _and_ functional for SCHED_NORMAL and SCHED_BATCH.

--
Thanks for your time,
MCP