From: Peter Zijlstra <peterz@infradead.org>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Mike Galbraith <efault@gmx.de>,
shenghui <crosslonelyover@gmail.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] avoid race condition in pick_next_task_fair in kernel/sched_fair.c
Date: Wed, 22 Dec 2010 18:08:38 +0100 [thread overview]
Message-ID: <1293037718.2170.155.camel@laptop> (raw)
In-Reply-To: <20101222151434.GW10557@genesis.frugalware.org>
On Wed, 2010-12-22 at 16:14 +0100, Miklos Vajna wrote:
> kernel-build is a git build using the config I already sent and after a
> 'git checkout v2.6.36'. I can try to build master as well, so far what I
> saw is that the bug occurs there as well, but less frequently, so maybe
> that's a bit harder to debug.
Right, so I've got v2.6.36 exploding, current -git and -tip won't
explode for me, tried both about 20 times. So I'll try and figure out
wth makes .36 explode and then see if further kernel still suffer that
problem.
next prev parent reply other threads:[~2010-12-22 17:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 7:10 [PATCH] avoid race condition in pick_next_task_fair in kernel/sched_fair.c shenghui
2010-06-29 10:43 ` Peter Zijlstra
2010-06-29 11:24 ` shenghui
2010-06-29 11:35 ` Peter Zijlstra
2010-06-29 12:44 ` shenghui
2010-12-19 2:03 ` Miklos Vajna
2010-12-22 0:22 ` Miklos Vajna
2010-12-22 8:29 ` Peter Zijlstra
2010-12-22 8:41 ` Peter Zijlstra
2010-12-22 8:41 ` Mike Galbraith
2010-12-22 9:07 ` Peter Zijlstra
2010-12-22 13:31 ` Miklos Vajna
2010-12-22 14:00 ` Peter Zijlstra
2010-12-22 14:11 ` Peter Zijlstra
2010-12-22 15:14 ` Miklos Vajna
2010-12-22 15:25 ` Peter Zijlstra
2010-12-22 17:08 ` Peter Zijlstra [this message]
2010-12-22 17:16 ` Ingo Molnar
2010-12-22 17:25 ` Peter Zijlstra
2010-12-22 20:36 ` Peter Zijlstra
2010-12-23 2:08 ` Yong Zhang
2010-12-23 12:12 ` Peter Zijlstra
2010-12-23 12:33 ` Peter Zijlstra
2010-12-23 18:24 ` Peter Zijlstra
[not found] ` <1293132304.6798.6.camel@marge.simson.net>
[not found] ` <1293132862.25981.22.camel@laptop>
[not found] ` <1293187425.7138.2.camel@marge.simson.net>
[not found] ` <1293188091.25981.200.camel@laptop>
[not found] ` <1293192999.18035.4.camel@marge.simson.net>
2010-12-24 15:59 ` [PATCH] sched, cgroup: Use exit hook to avoid use-after-free crash Peter Zijlstra
2010-12-24 16:40 ` Miklos Vajna
2010-12-24 16:48 ` Mike Galbraith
2010-12-24 17:07 ` Peter Zijlstra
2010-12-24 17:24 ` Mike Galbraith
2010-12-25 17:55 ` Balbir Singh
2010-12-25 20:59 ` Paul Menage
2011-01-03 7:06 ` Peter Zijlstra
2010-12-29 15:25 ` Ingo Molnar
2010-12-29 23:07 ` Miklos Vajna
2010-12-31 10:04 ` Mike Galbraith
2010-12-31 10:46 ` Miklos Vajna
2010-12-31 8:32 ` [PATCH] " Mike Galbraith
2011-01-03 8:21 ` Peter Zijlstra
2011-01-04 14:19 ` [tip:sched/core] sched, autogroup: Fix reference leak tip-bot for Mike Galbraith
2011-01-04 14:57 ` Oleg Nesterov
2011-01-04 19:06 ` Mike Galbraith
2011-01-19 19:04 ` [tip:sched/urgent] sched, cgroup: Use exit hook to avoid use-after-free crash tip-bot for Peter Zijlstra
2010-12-22 21:11 ` [PATCH] avoid race condition in pick_next_task_fair in kernel/sched_fair.c Miklos Vajna
2010-12-22 23:39 ` Miklos Vajna
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=1293037718.2170.155.camel@laptop \
--to=peterz@infradead.org \
--cc=crosslonelyover@gmail.com \
--cc=efault@gmx.de \
--cc=greg@kroah.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vmiklos@frugalware.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