From: Petr Vorel <pvorel@suse.cz>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>, Cyril Hrubis <chrubis@suse.cz>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/3] sched/rt fixes for 5.15, 5.10, 5.4
Date: Thu, 22 Feb 2024 16:36:50 +0100 [thread overview]
Message-ID: <20240222153650.GA1366077@pevik> (raw)
In-Reply-To: <20240222151333.1364818-5-pvorel@suse.cz>
Hi all,
> Cyril Hrubis (3):
> sched/rt: Fix sysctl_sched_rr_timeslice intial value
> sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset
> sched/rt: Disallow writing invalid values to sched_rt_period_us
I'm sorry for the noise, while this patchset is working for 5.15 and 5.10,
it fails to compile on 5.4 due missing SYSCTL_ONE:
kernel/sysctl.c:477:14: error: ‘SYSCTL_NEG_ONE’ undeclared here (not in a function); did you mean ‘SYSCTL_ONE’?
.extra1 = SYSCTL_NEG_ONE,
^~~~~~~~~~~~~~
SYSCTL_ONE
This is because 78e36f3b0dae ("sysctl: move some boundary constants from
sysctl.c to sysctl_vals") was backported from 5.17 to 5.15 and 5.10 but not to
5.4. If you agree on the same approach I took for 4.19 (create variable in
kernel/sysctl.c) and send patch for 5.4.
Or, we can backport just to >= 5.10. Cyril and others who merged this obviously
did not consider this important enough to backport. OTOH we have 2 LTP tests
which are testing these:
* sched_rr_get_interval01 tests c7fcb99877f9 (on non-default CONFIG_HZ)
* the other two commits are tested by proc_sched_rt01
Therefore I thought fixing at least 6.* would be good.
Kind regards,
Petr
> kernel/sched/rt.c | 10 +++++-----
> kernel/sysctl.c | 4 ++++
> 2 files changed, 9 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2024-02-22 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 15:13 [PATCH 0/3] sched/rt fixes for 4.19 Petr Vorel
2024-02-22 15:13 ` [PATCH 1/3] sched/rt: Fix sysctl_sched_rr_timeslice intial value Petr Vorel
2024-02-22 15:13 ` [PATCH 2/3] sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset Petr Vorel
2024-02-22 15:13 ` [PATCH 3/3] sched/rt: Disallow writing invalid values to sched_rt_period_us Petr Vorel
2024-02-22 15:13 ` [PATCH 0/3] sched/rt fixes for 5.15, 5.10, 5.4 Petr Vorel
2024-02-22 15:36 ` Petr Vorel [this message]
2024-02-22 15:13 ` [PATCH 1/3] sched/rt: Fix sysctl_sched_rr_timeslice intial value Petr Vorel
2024-02-22 15:13 ` [PATCH 2/3] sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset Petr Vorel
2024-02-22 15:13 ` [PATCH 3/3] sched/rt: Disallow writing invalid values to sched_rt_period_us Petr Vorel
2024-02-22 15:13 ` [PATCH 0/2] sched/rt fixes for 6.1 Petr Vorel
2024-02-22 15:13 ` [PATCH 1/2] sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset Petr Vorel
2024-02-22 15:13 ` [PATCH 2/2] sched/rt: Disallow writing invalid values to sched_rt_period_us Petr Vorel
2024-02-22 15:13 ` [PATCH 0/1] sched/rt fixes for 6.6 Petr Vorel
2024-02-22 15:13 ` [PATCH 1/1] sched/rt: Disallow writing invalid values to sched_rt_period_us Petr Vorel
2024-02-22 15:32 ` [PATCH 0/3] sched/rt fixes for 4.19 Greg Kroah-Hartman
2024-02-22 16:50 ` Petr Vorel
2024-02-22 17:19 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240222153650.GA1366077@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox