From: "Daniel K." <dk@uw.no>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@elte.hu, menage@google.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>
Subject: Re: [BUG: NULL pointer dereference] cgroups and RT scheduling interact badly.
Date: Wed, 18 Jun 2008 15:35:05 +0200 [thread overview]
Message-ID: <48590F09.7000406@uw.no> (raw)
In-Reply-To: <1213789854.16944.216.camel@twins>
Peter Zijlstra wrote:
> On Tue, 2008-06-17 at 21:48 +0000, Daniel K. wrote:
>> I had almost given up trying to break it, but then this happened.
>>
>> [...]
>
> Ah, fun a race between dequeueing because of runtime quota and
> requeueing because of RR slice length.
>
>> Yes, I realize I'm starting to sound like a broken record.
>
> Ah, don't worry - I was just hoping there was an end to the amount of
> glaring bugs in my code :-/
:)
> Reproducing was a bit harder than for you, it took me a whole minute of
> runtime and setting the runtime limit above the RR slice length (and
> realizing you're running RR, not FIFO).
>
> The below patch (on top of the other one) seems to not make it crash
> this case for at least 15 minutes.
I am happy to say that this nailed it squarely on the head. I no longer
see any of the Oops'es I could quite easily trigger before. I added my
Tested-by, please add it to the patch you sent yesterday as well.
I still have a few gripes with RR scheduling, but that is a topic for
another mail.
> ---
> Subject: sched: rt-group: fix RR buglet
> From: Peter Zijlstra <a.p.zijlstra@chello.nl>
>
> In tick_task_rt() we first call update_curr_rt() which can dequeue a runqueue
> due to it running out of runtime, and then we try to requeue it, of it also
> having exhausted its RR quota. Obviously requeueing something that is no longer
> on the runqueue will not have the expected result.
>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Tested-by: Daniel K. <dk@uw.no>
> ---
> kernel/sched_rt.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> Index: linux-2.6/kernel/sched_rt.c
> ===================================================================
> --- linux-2.6.orig/kernel/sched_rt.c
> +++ linux-2.6/kernel/sched_rt.c
> @@ -549,8 +549,10 @@ static
> void requeue_rt_entity(struct rt_rq *rt_rq, struct sched_rt_entity *rt_se)
> {
> struct rt_prio_array *array = &rt_rq->active;
> + struct list_head *queue = array->queue + rt_se_prio(rt_se);
>
> - list_move_tail(&rt_se->run_list, array->queue + rt_se_prio(rt_se));
> + if (on_rt_rq(rt_se))
> + list_move_tail(&rt_se->run_list, queue);
> }
>
> static void requeue_task_rt(struct rq *rq, struct task_struct *p)
Daniel K.
next prev parent reply other threads:[~2008-06-18 13:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 22:26 [BUG: NULL pointer dereference] cgroups and RT scheduling interact badly Daniel K.
2008-06-16 10:34 ` Peter Zijlstra
2008-06-16 13:14 ` Daniel K.
2008-06-16 13:51 ` Peter Zijlstra
2008-06-16 14:39 ` Peter Zijlstra
2008-06-16 15:11 ` Daniel K.
2008-06-16 15:18 ` Peter Zijlstra
2008-06-17 8:49 ` Peter Zijlstra
2008-06-17 12:25 ` Daniel K.
2008-06-17 12:46 ` Peter Zijlstra
2008-06-17 20:01 ` Peter Zijlstra
2008-06-17 21:03 ` Dmitry Adamushko
2008-06-17 21:48 ` Daniel K.
2008-06-18 11:50 ` Peter Zijlstra
2008-06-18 13:35 ` Daniel K. [this message]
2008-06-18 14:12 ` 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=48590F09.7000406@uw.no \
--to=dk@uw.no \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.