From: Tejun Heo <tj@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Avi Kivity <avi@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Slaby <jirislaby@gmail.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mm-commits@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, the arch/x86 maintainers <x86@kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: WARNING: kernel/smp.c:292 smp_call_function_single [Was: mmotm 2009-11-24-16-47 uploaded]
Date: Mon, 30 Nov 2009 19:45:34 +0900 [thread overview]
Message-ID: <4B13A24E.1080100@kernel.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911301055000.24119@localhost.localdomain>
Hello,
On 11/30/2009 07:02 PM, Thomas Gleixner wrote:
> No, it _CANNOT_ be preempted at that point:
>
> schedule()
> {
> preempt_disable();
>
> switch_to();
>
> preempt_enable();
> }
Yes, you're right.
>> For the time being, maybe it's best to back out the fix given that the
>> only architecture which may be affected by the original bug is ia64
>> which is the only one with both kvm and the unlocked context switch.
>
> Do you have a pointer to the original bug report ?
Nope, I was referring to the imaginary race condition, so there's no
bug to worry about. The only problem is the asymmetry between in and
out callbacks. Then again, it's not really possible to match them on
unlocked ctxsw archs anyway, so I guess the only thing to do is to
document the context difference between in and out.
Sorry about the fuss. I'll send out patch to revert it and document
the difference.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-11-30 10:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 0:47 mmotm 2009-11-24-16-47 uploaded akpm
2009-11-25 15:12 ` BUG at scsi_lib.c:1108 [Was: mmotm 2009-11-24-16-47 uploaded] Jiri Slaby
2009-11-25 15:19 ` James Bottomley
2009-11-25 20:22 ` Jiri Slaby
2009-11-25 21:13 ` Neil Brown
2009-11-26 10:17 ` Boaz Harrosh
2009-11-27 4:17 ` Neil Brown
2009-11-27 10:20 ` Jiri Slaby
2009-11-26 1:46 ` mmotm 2009-11-24-16-47 uploaded (gpio_max7301) Randy Dunlap
2009-11-28 16:21 ` Wolfram Sang
2009-12-15 22:43 ` Andrew Morton
2009-12-15 22:46 ` Randy Dunlap
2009-12-15 23:10 ` Andrew Morton
2009-12-16 11:30 ` Wolfram Sang
2009-11-27 10:33 ` ugly sound output (intel-hda) [was: mmotm 2009-11-24-16-47 uploaded] Jiri Slaby
2009-11-27 10:45 ` Takashi Iwai
2009-11-27 11:07 ` Jiri Slaby
2009-11-27 11:18 ` Takashi Iwai
2009-11-27 12:22 ` Jiri Slaby
2009-11-27 12:26 ` Takashi Iwai
2009-11-27 15:03 ` WARNING: kernel/smp.c:292 smp_call_function_single [Was: " Jiri Slaby
2009-11-27 15:17 ` Peter Zijlstra
2009-11-27 16:37 ` Thomas Gleixner
2009-11-27 16:44 ` Thomas Gleixner
2009-11-28 12:12 ` Avi Kivity
2009-11-30 8:58 ` Tejun Heo
2009-11-30 9:41 ` Avi Kivity
2009-11-30 10:02 ` Thomas Gleixner
2009-11-30 10:45 ` Tejun Heo [this message]
2009-11-30 11:02 ` [PATCH tip/sched/urgent] sched: revert 498657a478c60be092208422fefa9c7b248729c2 Tejun Heo
2009-11-30 11:13 ` Avi Kivity
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=4B13A24E.1080100@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=jirislaby@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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