From: Zefan Li <lizefan@huawei.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Stefan Bader <stefan.bader@canonical.com>
Subject: [PATCH] sched, autogroup: Fix failure when writing to cpu.rt_runtime_us
Date: Thu, 5 Feb 2015 16:33:24 +0800 [thread overview]
Message-ID: <54D32AD4.1060003@huawei.com> (raw)
This is how to reproduce the bug:
int main() {
struct sched_param param = {.sched_priority=1};
if (fork() > 0)
exit(0);
setsid();
if (sched_setscheduler(0, SCHED_RR, ¶m) < 0){
perror("failed to sched_setscheduler()");
return -1;
}
while(1)
;
}
# ./test
# mount -t cgroup -o cpu xxx /cgroup
# cat /cgroup/cpu.rt_runtime_us
950000
# echo 940000 > /cgroup/cpu.rt_runtime_us
Device or Resource busy
An autogroup has been created and there's an RT task in it. RT tasks in
autogroups are redirected to the root group and task_group() should
return &root_task_group, but it's broken and returns the autogroup.
We should reset p->sched_task_group when changing a normal task to an
RT task which is in autogroup.
Fixes: 8323f26ce342 ("sched: Fix race in task_group()")
Cc: <stable@vger.kernel.org> # 3.6+
Reported-by: Zhang Wei <zhangwei555@huawei.com>
Signed-off-by: Zefan Li <lizefan@huawei.com>
---
kernel/sched/core.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 89e7283..fccde96 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3414,6 +3414,7 @@ static int __sched_setscheduler(struct task_struct *p,
const struct sched_class *prev_class;
struct rq *rq;
int reset_on_fork;
+ bool reset_task_group = false;
/* may grab non-irq protected spin_locks */
BUG_ON(in_interrupt());
@@ -3546,10 +3547,13 @@ change:
* assigned.
*/
if (rt_bandwidth_enabled() && rt_policy(policy) &&
- task_group(p)->rt_bandwidth.rt_runtime == 0 &&
- !task_group_is_autogroup(task_group(p))) {
- task_rq_unlock(rq, p, &flags);
- return -EPERM;
+ task_group(p)->rt_bandwidth.rt_runtime == 0) {
+ if (!task_group_is_autogroup(task_group(p))) {
+ task_rq_unlock(rq, p, &flags);
+ return -EPERM;
+ } else {
+ reset_task_group = true;
+ }
}
#endif
#ifdef CONFIG_SMP
@@ -3615,6 +3619,9 @@ change:
prev_class = p->sched_class;
__setscheduler(rq, p, attr);
+ if (reset_task_group)
+ p->sched_task_group = &root_task_group;
+
if (running)
p->sched_class->set_curr_task(rq);
if (queued) {
--
1.8.0.2
next reply other threads:[~2015-02-05 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 8:33 Zefan Li [this message]
2015-02-05 14:25 ` [PATCH] sched, autogroup: Fix failure when writing to cpu.rt_runtime_us Peter Zijlstra
2015-02-06 1:30 ` Zefan Li
2015-02-06 10:58 ` Peter Zijlstra
2015-02-07 7:02 ` Zefan Li
2015-02-09 11:22 ` Peter Zijlstra
2015-02-09 11:27 ` Peter Zijlstra
2015-02-18 17:09 ` [tip:sched/core] sched/rt: Avoid obvious configuration fail tip-bot for Peter Zijlstra
2015-02-10 1:26 ` [PATCH] sched, autogroup: Fix failure when writing to cpu.rt_runtime_us Zefan Li
2015-02-18 17:09 ` [tip:sched/core] sched/autogroup: Fix failure to set cpu.rt_runtime_us tip-bot for Peter Zijlstra
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=54D32AD4.1060003@huawei.com \
--to=lizefan@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stefan.bader@canonical.com \
--cc=umgwanakikbuti@gmail.com \
/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