LKML Archive on
help / color / mirror / Atom feed
From: "tip-bot2 for Quentin Perret" <>
Cc: Wei Wang <>, Quentin Perret <>,
	"Peter Zijlstra (Intel)" <>,
	Dietmar Eggemann <>,
	Qais Yousef <>,,
Subject: [tip: sched/core] sched: Skip priority checks with SCHED_FLAG_KEEP_PARAMS
Date: Fri, 06 Aug 2021 12:57:49 -0000	[thread overview]
Message-ID: <162825466988.395.169396099784504532.tip-bot2@tip-bot2> (raw)
In-Reply-To: <>

The following commit has been merged into the sched/core branch of tip:

Commit-ID:     f4dddf90d58d77b48492b775868af4041a217f4c
Author:        Quentin Perret <>
AuthorDate:    Thu, 05 Aug 2021 11:21:54 +01:00
Committer:     Peter Zijlstra <>
CommitterDate: Fri, 06 Aug 2021 14:25:25 +02:00

sched: Skip priority checks with SCHED_FLAG_KEEP_PARAMS

SCHED_FLAG_KEEP_PARAMS can be passed to sched_setattr to specify that
the call must not touch scheduling parameters (nice or priority). This
is particularly handy for uclamp when used in conjunction with
SCHED_FLAG_KEEP_POLICY as that allows to issue a syscall that only
impacts uclamp values.

However, sched_setattr always checks whether the priorities and nice
values passed in sched_attr are valid first, even if those never get
used down the line. This is useless at best since userspace can
trivially bypass this check to set the uclamp values by specifying low
priorities. However, it is cumbersome to do so as there is no single
expression of this that skips both RT and CFS checks at once. As such,
userspace needs to query the task policy first with e.g. sched_getattr
and then set sched_attr.sched_priority accordingly. This is racy and
slower than a single call.

As the priority and nice checks are useless when SCHED_FLAG_KEEP_PARAMS
is specified, simply inherit them in this case to match the policy
inheritance of SCHED_FLAG_KEEP_POLICY.

Reported-by: Wei Wang <>
Signed-off-by: Quentin Perret <>
Signed-off-by: Peter Zijlstra (Intel) <>
Reviewed-by: Dietmar Eggemann <>
Reviewed-by: Qais Yousef <>
 kernel/sched/core.c | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index df0480a..433b400 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -7328,6 +7328,16 @@ err_size:
 	return -E2BIG;
+static void get_params(struct task_struct *p, struct sched_attr *attr)
+	if (task_has_dl_policy(p))
+		__getparam_dl(p, attr);
+	else if (task_has_rt_policy(p))
+		attr->sched_priority = p->rt_priority;
+	else
+		attr->sched_nice = task_nice(p);
  * sys_sched_setscheduler - set/change the scheduler policy and RT priority
  * @pid: the pid in question.
@@ -7389,6 +7399,8 @@ SYSCALL_DEFINE3(sched_setattr, pid_t, pid, struct sched_attr __user *, uattr,
 	if (likely(p)) {
+		if (attr.sched_flags & SCHED_FLAG_KEEP_PARAMS)
+			get_params(p, &attr);
 		retval = sched_setattr(p, &attr);
@@ -7537,12 +7549,7 @@ SYSCALL_DEFINE4(sched_getattr, pid_t, pid, struct sched_attr __user *, uattr,
 	kattr.sched_policy = p->policy;
 	if (p->sched_reset_on_fork)
 		kattr.sched_flags |= SCHED_FLAG_RESET_ON_FORK;
-	if (task_has_dl_policy(p))
-		__getparam_dl(p, &kattr);
-	else if (task_has_rt_policy(p))
-		kattr.sched_priority = p->rt_priority;
-	else
-		kattr.sched_nice = task_nice(p);
+	get_params(p, &kattr);
 	kattr.sched_flags &= SCHED_FLAG_ALL;

      reply	other threads:[~2021-08-06 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 10:21 [PATCH v5 0/2] A couple of uclamp fixes Quentin Perret
2021-08-05 10:21 ` [PATCH v5 1/2] sched: Fix UCLAMP_FLAG_IDLE setting Quentin Perret
2021-08-06 12:57   ` [tip: sched/core] " tip-bot2 for Quentin Perret
2021-08-05 10:21 ` [PATCH v5 2/2] sched: Skip priority checks with SCHED_FLAG_KEEP_PARAMS Quentin Perret
2021-08-06 12:57   ` tip-bot2 for Quentin Perret [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162825466988.395.169396099784504532.tip-bot2@tip-bot2 \ \ \ \ \ \ \ \ \ \
    --subject='Re: [tip: sched/core] sched: Skip priority checks with SCHED_FLAG_KEEP_PARAMS' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).