From: Ingo Molnar <mingo@elte.hu>
To: Avi Kivity <avi@redhat.com>
Cc: Tejun Heo <tj@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 2.6.32-rc6] sched, kvm: fix race condition involving sched_in_preempt_notifers
Date: Mon, 30 Nov 2009 11:00:49 +0100 [thread overview]
Message-ID: <20091130100049.GA7054@elte.hu> (raw)
In-Reply-To: <4B13942E.3000002@redhat.com>
* Avi Kivity <avi@redhat.com> wrote:
> On 11/30/2009 11:09 AM, Tejun Heo wrote:
> >
> >>
> >>> but we want to do sched.c changes via
> >>>the scheduler tree.
> >So, this one was a bust. Given that the only platform which might
> >have been affected by the original bug is ia64 and it's very unlikely
> >to happen. I think reverting this from sched/urgent would be the
> >right thing to do at this point if the branch is headed for another
> >push to Linus. Avi, what do you think?
>
> I agree.
that sched/urgent commit is not queued up for 2.6.32 (Linus indicated
there wont be an -rc9), it spills over to the 2.6.33 merge window.
Ingo
next prev parent reply other threads:[~2009-11-30 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 9:33 [PATCH 2.6.32-rc6] sched, kvm: fix race condition involving sched_in_preempt_notifers Tejun Heo
2009-11-13 9:55 ` Ingo Molnar
2009-11-14 13:06 ` Avi Kivity
2009-11-30 9:09 ` Tejun Heo
2009-11-30 9:45 ` Avi Kivity
2009-11-30 10:00 ` Ingo Molnar [this message]
2009-11-30 10:11 ` Avi Kivity
2009-11-30 11:41 ` [PATCH UPDATED " Tejun Heo
2009-11-15 10:29 ` [tip:sched/urgent] sched, kvm: Fix " tip-bot for Tejun Heo
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=20091130100049.GA7054@elte.hu \
--to=mingo@elte.hu \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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