From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Lennart Poettering <lennart@poettering.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] sched: allow unsetting SCHED_RESET_ON_FORK when new policy is not realtime
Date: Wed, 17 Oct 2012 23:18:36 +0200 [thread overview]
Message-ID: <507F20AC.6000308@canonical.com> (raw)
When implementing SIGXCPU handling for a thread boosted with rtkit to realtime
priority, I noticed that sched_setscheduler(somepid, SCHED_OTHER) would return
-EPERM because the thread was previously SCHED_RR | SCHED_RESET_ON_FORK,
and looking from the code that flag cannot be reset without sufficient rights.
sched_setscheduler(somepid, SCHED_OTHER | SCHED_RESET_ON_FORK) which worked,
and seems to be the only way to remove realtime priority set by rtkit on all
kernels since the patch was introduced.
This patch allows SCHED_RESET_ON_FORK to be removed when the user sets a new
policy on itself without realtime.
Cc: Stable <stable@vger.kernel.org> [v2.6.32+]
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 2d8927f..4c0712a 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3757,6 +3757,12 @@ recheck:
if (param->sched_priority > p->rt_priority &&
param->sched_priority > rlim_rtprio)
return -EPERM;
+
+ /* Normal users shall not reset the
+ * sched_reset_on_fork flag
+ */
+ if (p->sched_reset_on_fork && !reset_on_fork)
+ return -EPERM;
}
/*
@@ -3771,10 +3777,6 @@ recheck:
/* can't change other user's priorities */
if (!check_same_owner(p))
return -EPERM;
-
- /* Normal users shall not reset the sched_reset_on_fork flag */
- if (p->sched_reset_on_fork && !reset_on_fork)
- return -EPERM;
}
if (user) {
next reply other threads:[~2012-10-17 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 21:18 Maarten Lankhorst [this message]
2012-10-17 21:41 ` [PATCH] sched: allow unsetting SCHED_RESET_ON_FORK when new policy is not realtime Maarten Lankhorst
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=507F20AC.6000308@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=lennart@poettering.net \
--cc=linux-kernel@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