From: tip-bot for Tejun Heo <tj@kernel.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
a.p.zijlstra@chello.nl, tj@kernel.org, tglx@linutronix.de,
avi@redhat.com, mingo@elte.hu
Subject: [tip:sched/urgent] sched, kvm: Fix race condition involving sched_in_preempt_notifers
Date: Sun, 15 Nov 2009 10:29:08 GMT [thread overview]
Message-ID: <tip-498657a478c60be092208422fefa9c7b248729c2@git.kernel.org> (raw)
In-Reply-To: <4AFD2801.7020900@kernel.org>
Commit-ID: 498657a478c60be092208422fefa9c7b248729c2
Gitweb: http://git.kernel.org/tip/498657a478c60be092208422fefa9c7b248729c2
Author: Tejun Heo <tj@kernel.org>
AuthorDate: Fri, 13 Nov 2009 18:33:53 +0900
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sun, 15 Nov 2009 09:59:54 +0100
sched, kvm: Fix race condition involving sched_in_preempt_notifers
In finish_task_switch(), fire_sched_in_preempt_notifiers() is
called after finish_lock_switch().
However, depending on architecture, preemption can be enabled after
finish_lock_switch() which breaks the semantics of preempt
notifiers.
So move it before finish_arch_switch(). This also makes the in-
notifiers symmetric to out- notifiers in terms of locking - now
both are called under rq lock.
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Avi Kivity <avi@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <4AFD2801.7020900@kernel.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index 701eca4..cea2bea 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -2758,9 +2758,9 @@ static void finish_task_switch(struct rq *rq, struct task_struct *prev)
prev_state = prev->state;
finish_arch_switch(prev);
perf_event_task_sched_in(current, cpu_of(rq));
+ fire_sched_in_preempt_notifiers(current);
finish_lock_switch(rq, prev);
- fire_sched_in_preempt_notifiers(current);
if (mm)
mmdrop(mm);
if (unlikely(prev_state == TASK_DEAD)) {
prev parent reply other threads:[~2009-11-15 10:29 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
2009-11-30 10:11 ` Avi Kivity
2009-11-30 11:41 ` [PATCH UPDATED " Tejun Heo
2009-11-15 10:29 ` tip-bot for Tejun Heo [this message]
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=tip-498657a478c60be092208422fefa9c7b248729c2@git.kernel.org \
--to=tj@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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.