From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <andi@firstfloor.org>,
"H. Peter Anvin" <hpa@kernel.org>, Dave Jones <davej@redhat.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask_bitmask+0xc3/0xe0()
Date: Fri, 22 Aug 2008 23:44:18 -0700 [thread overview]
Message-ID: <48AFB1C2.5020806@zytor.com> (raw)
In-Reply-To: <48AFB14F.7090407@goop.org>
Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> Well, smp_call_function_single already does all necessary locking; it
>> makes more sense for it to check that what it's about to call still
>> exists while inside the lock, instead of requiring the higher layers
>> to guarantee that cannot happen on it. This is simply a matter of the
>> cost of checking at this point being quite low.
>
> It does, already doesn't it? Hm, smp_call_function_mask() ands the
> provided mask with the online mask, but it doesn't look like
> smp_call_function_single() does the equivalent.
It doesn't, and that's how this bug was introduced. It's a trivial add
(see test patch already posted) and should hardly matter in terms of
execution time.
I'll write up a clean patch with all the error propagation tomorrow or
Sunday.
-hpa
next prev parent reply other threads:[~2008-08-23 6:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 19:51 latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask_bitmask+0xc3/0xe0() Vegard Nossum
2008-08-20 1:39 ` Andi Kleen
2008-08-20 6:26 ` Vegard Nossum
2008-08-22 0:36 ` Dave Jones
2008-08-22 2:13 ` H. Peter Anvin
2008-08-22 2:28 ` Andi Kleen
2008-08-22 6:24 ` H. Peter Anvin
2008-08-22 9:35 ` Andi Kleen
2008-08-22 16:41 ` H. Peter Anvin
2008-08-23 6:42 ` Jeremy Fitzhardinge
2008-08-23 6:44 ` H. Peter Anvin [this message]
2008-08-22 11:13 ` adobriyan
2008-08-24 9:20 ` Vegard Nossum
2008-08-24 16:43 ` H. Peter Anvin
2008-08-24 17:17 ` H. Peter Anvin
2008-08-24 17:22 ` Vegard Nossum
2008-08-24 17:45 ` Vegard Nossum
2008-08-24 17:59 ` H. Peter Anvin
2008-08-24 18:13 ` Dave Jones
2008-08-25 18:31 ` Vegard Nossum
2008-08-25 18:38 ` Dave Jones
2008-08-25 18:36 ` Andi Kleen
2008-08-25 18:54 ` Dave Jones
2008-08-25 19:39 ` Andi Kleen
2008-08-25 19:50 ` Dave Jones
2008-08-25 20:36 ` Andi Kleen
2008-08-25 20:47 ` Dave Jones
2008-08-25 21:24 ` Arjan van de Ven
2008-08-25 19:08 ` H. Peter Anvin
2008-08-25 19:13 ` Dave Jones
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=48AFB1C2.5020806@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=davej@redhat.com \
--cc=hpa@kernel.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=vegard.nossum@gmail.com \
--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