linux-kernel - Re: [PATCH v3 1/1] hrtimer: use and report correct timerslack values for realtime tasks

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: <8734n7per0.ffs@tglx>
Date: Wed, 14 Aug 2024 12:42:27 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: "MOESSBAUER, Felix" <felix.moessbauer@...mens.com>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: "qyousef@...alina.io" <qyousef@...alina.io>, "frederic@...nel.org"
 <frederic@...nel.org>, "Kiszka, Jan" <jan.kiszka@...mens.com>,
 "bigeasy@...utronix.de" <bigeasy@...utronix.de>,
 "anna-maria@...utronix.de" <anna-maria@...utronix.de>
Subject: Re: [PATCH v3 1/1] hrtimer: use and report correct timerslack
 values for realtime tasks

On Tue, Aug 13 2024 at 10:23, Felix MOESSBAUER wrote:
> On Tue, 2024-08-13 at 11:45 +0200, Thomas Gleixner wrote:
>> Why are you declaring that a RT task has to have 0 slack if we are
>> lifting the hard coded slack zeroing in the hrtimer functions?
>
> This is what the manpage states [1]:
>
> + Timer slack is not applied to threads that are scheduled under a
> + real-time scheduling policy (see sched_setscheduler(2)).
>
> [1] https://man7.org/linux/man-pages/man2/PR_SET_TIMERSLACK.2const.html

Fair enough. Mention it in the changelog please.

Thanks,

        tglx