From: Yinghai Lu <yinghai@kernel.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>, Sam Ravnborg <sam@ravnborg.org>,
David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
mel@csn.ul.ie
Subject: Re: [BUG] next-20081216 - WARNING: at kernel/smp.c:333 smp_call_function_mask
Date: Fri, 26 Dec 2008 23:14:13 -0800 [thread overview]
Message-ID: <4955D5C5.90407@kernel.org> (raw)
In-Reply-To: <20081227071138.GA4530@linux.vnet.ibm.com>
Kamalesh Babulal wrote:
> * Ingo Molnar <mingo@elte.hu> [2008-12-26 19:17:34]:
>
>> * Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>>
>>>> how about the patch below, does that work too? (after removing
>>>> Yinghai's patch)
>>> Hi Ingo,
>>>
>>> Kernel crashes with the same trace, after the applying the patch.
>> okay, thanks - does the below cleaner variant of Yinghai's patch solve the
>> problem too?
>>
>> Ingo
>>
>> -------------------->
>> From 9c93fc72ec95dc97d65b840978f9d605f4e5823a Mon Sep 17 00:00:00 2001
>> From: Yinghai Lu <yinghai@kernel.org>
>> Date: Fri, 26 Dec 2008 02:05:47 -0800
>> Subject: [PATCH] sparseirq: work around compiler optimizing away __weak functions
>>
>> Impact: fix panic on null pointer with sparseirq
>>
>> Some GCC versions seem to inline the weak global function,
>> when that function is empty.
>>
>> Work it around, by putting a barrier into the function.
>>
>> Signed-off-by: Yinghai <yinghai@kernel.org>
>> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>> ---
>> init/main.c | 9 +++++++++
>> kernel/irq/handle.c | 3 ++-
>> 2 files changed, 11 insertions(+), 1 deletions(-)
>>
>> diff --git a/init/main.c b/init/main.c
>> index c1f999a..841d2b2 100644
>> --- a/init/main.c
>> +++ b/init/main.c
>> @@ -531,20 +531,29 @@ static void __init boot_cpu_init(void)
>> cpu_set(cpu, cpu_possible_map);
>> }
>>
>> +/*
>> + * The barriers are needed to keep a GCC bug from optimizing
>> + * away these weak functions:
>> + */
>> +
>> void __init __weak smp_setup_processor_id(void)
>> {
>> + barrier();
>> }
>>
>> void __init __weak thread_info_cache_init(void)
>> {
>> + barrier();
>> }
>>
>> void __init __weak arch_early_irq_init(void)
>> {
>> + barrier();
>> }
>>
>> void __init __weak early_irq_init(void)
>> {
>> + barrier();
>> arch_early_irq_init();
>> }
>>
>> diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
>> index 06b05a4..a6d16a4 100644
>> --- a/kernel/irq/handle.c
>> +++ b/kernel/irq/handle.c
>> @@ -86,8 +86,9 @@ void init_kstat_irqs(struct irq_desc *desc, int cpu, int nr)
>> desc->kstat_irqs = (unsigned int *)ptr;
>> }
>>
>> -void __attribute__((weak)) arch_init_chip_data(struct irq_desc *desc, int cpu)
>> +void __weak arch_init_chip_data(struct irq_desc *desc, int cpu)
>> {
>> + barrier();
>> }
>>
>> static void init_one_irq_desc(int irq, struct irq_desc *desc, int cpu)
>> --
>
> Hi Ingo,
>
> Kernel still crashes after applying the patch,
>
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> ACPI: Core revision 20080926
> Setting APIC routing to flat
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
> IP: [<ffffffff8021f8fd>] add_pin_to_irq_cpu+0x14/0x73
that is interesting, barrier() doesn't work, we do need that printk?
YH
next prev parent reply other threads:[~2008-12-27 7:15 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 11:37 linux-next: Tree for December 16 Stephen Rothwell
2008-12-16 23:26 ` Andrew Morton
2008-12-17 6:59 ` linux-next: mtd tree build failures (Was: Re: linux-next: Tree for December 16) Stephen Rothwell
2008-12-17 9:32 ` Artem Bityutskiy
2008-12-17 9:57 ` Stephen Rothwell
2008-12-17 7:07 ` linux-next: Tree for December 16 Artem Bityutskiy
2008-12-17 7:08 ` next-20081216 - powerpc link error 'dynreloc miscount' Kamalesh Babulal
2008-12-17 7:28 ` Sam Ravnborg
2008-12-17 7:30 ` Stephen Rothwell
2008-12-19 10:54 ` [BUG] next-20081216 - WARNING: at kernel/smp.c:333 smp_call_function_mask Kamalesh Babulal
2008-12-19 11:51 ` Yinghai Lu
2008-12-19 13:46 ` Kamalesh Babulal
2008-12-19 21:02 ` Yinghai Lu
2008-12-23 13:21 ` Kamalesh Babulal
2008-12-23 21:09 ` Yinghai Lu
2008-12-24 16:34 ` Kamalesh Babulal
2008-12-24 20:34 ` Yinghai Lu
2008-12-26 9:12 ` Kamalesh Babulal
2008-12-26 10:05 ` Yinghai Lu
2008-12-26 10:27 ` Sam Ravnborg
2008-12-26 13:33 ` Ingo Molnar
2008-12-26 13:42 ` [PATCH] kbuild, sparseirq: work around GCC bug with __weak aliases Ingo Molnar
2008-12-27 4:09 ` Paul Mackerras
2008-12-27 10:59 ` Ingo Molnar
2008-12-28 23:27 ` Paul Mackerras
2008-12-26 15:28 ` [BUG] next-20081216 - WARNING: at kernel/smp.c:333 smp_call_function_mask Kamalesh Babulal
2008-12-26 15:33 ` Ingo Molnar
2008-12-26 17:04 ` Kamalesh Babulal
2008-12-26 18:17 ` Ingo Molnar
2008-12-27 7:11 ` Kamalesh Babulal
2008-12-27 7:14 ` Yinghai Lu [this message]
2008-12-27 7:39 ` Yinghai Lu
2008-12-27 8:37 ` Ingo Molnar
2008-12-27 8:39 ` Ingo Molnar
2008-12-27 11:21 ` Kamalesh Babulal
2008-12-27 11:24 ` Ingo Molnar
2008-12-27 11:57 ` Kamalesh Babulal
2008-12-27 12:26 ` Ingo Molnar
2008-12-27 15:29 ` Kamalesh Babulal
2008-12-27 21:10 ` Yinghai Lu
2008-12-28 12:55 ` Ingo Molnar
2008-12-28 16:11 ` Kamalesh Babulal
2008-12-28 23:09 ` Yinghai Lu
2008-12-27 5:05 ` [PATCH] perf_counter: more barrier in blank weak function Yinghai Lu
2008-12-27 5:06 ` [PATCH] kgdb: " Yinghai Lu
2008-12-27 8:17 ` Ingo Molnar
2008-12-27 8:34 ` Andrew Morton
2008-12-27 6:07 ` [PATCH] perf_counter: " KOSAKI Motohiro
2008-12-27 9:46 ` [BUG] next-20081216 - WARNING: at kernel/smp.c:333 smp_call_function_mask David Howells
2008-12-27 9:50 ` Ingo Molnar
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=4955D5C5.90407@kernel.org \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).