From: Glauber Costa <gcosta@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
glommer@gmail.com, pzijlstr@redhat.com, arjan@infradead.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 0/2] onlining cpus can break lockdep
Date: Thu, 21 Feb 2008 18:17:54 -0300 [thread overview]
Message-ID: <47BDEA82.8050508@redhat.com> (raw)
In-Reply-To: <20080221211209.GB9031@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
Ingo Molnar wrote:
> * Glauber Costa <gcosta@redhat.com> wrote:
>
>> Hi,
>>
>> While testing with hotplugging cpus today, I've came across a stack
>> trace generated by lockdep. The reason for that is that do_boot_cpu()
>> in smpboot_64.c ends up initializing a struct work_struct variable in
>> the stack.
>
> hm, could you post that trace?
Sure. To make it clearer where the problem is, I also added the attached
patch to my testing.
Trace is: (note the call to do_fork_idle)
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
key: ffff81003bdf9d18, name: c_idle.work
Pid: 11, comm: events/1 Not tainted 2.6.25-rc2 #129
Call Trace:
[<ffffffff8104f757>] static_obj+0x5d/0x74
[<ffffffff81052218>] __lock_acquire+0x8b5/0xc3e
[<ffffffff81042e7f>] run_workqueue+0x84/0x1df
[<ffffffff810529ef>] lock_acquire+0x91/0xbc
[<ffffffff81042e90>] run_workqueue+0x95/0x1df
[<ffffffff81291746>] do_fork_idle+0x0/0x20
[<ffffffff81042ed4>] run_workqueue+0xd9/0x1df
[<ffffffff81043951>] worker_thread+0x90/0x9b
[<ffffffff8104632a>] autoremove_wake_function+0x0/0x2e
[<ffffffff810438c1>] worker_thread+0x0/0x9b
[<ffffffff8104620c>] kthread+0x47/0x73
[<ffffffff812986c9>] trace_hardirqs_on_thunk+0x35/0x3a
[<ffffffff8100d0e8>] child_rip+0xa/0x12
[<ffffffff8100c67c>] restore_args+0x0/0x34
[<ffffffff81046095>] kthreadd+0x14a/0x16f
[<ffffffff81046095>] kthreadd+0x14a/0x16f
[<ffffffff810461c5>] kthread+0x0/0x73
[<ffffffff8100d0de>] child_rip+0x0/0x12
[-- Attachment #2: lockdep.patch --]
[-- Type: text/x-patch, Size: 461 bytes --]
diff --git a/kernel/lockdep.c b/kernel/lockdep.c
index 3574379..572df7d 100644
--- a/kernel/lockdep.c
+++ b/kernel/lockdep.c
@@ -730,6 +730,7 @@ register_lock_class(struct lockdep_map *
printk("INFO: trying to register non-static key.\n");
printk("the code is fine but needs lockdep annotation.\n");
printk("turning off the locking correctness validator.\n");
+ printk("key: %p, name: %s\n", lock->key, lock->name);
dump_stack();
return NULL;
prev parent reply other threads:[~2008-02-21 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 20:40 [PATCH 0/2] onlining cpus can break lockdep Glauber Costa
2008-02-21 20:40 ` [PATCH 1/2] turn c_idle into a pointer Glauber Costa
2008-02-21 20:40 ` [PATCH 2/2] make work have a static address in do_boot_cpu() Glauber Costa
2008-02-21 22:12 ` Peter Zijlstra
2008-02-21 22:57 ` Glauber Costa
2008-02-22 9:46 ` Ingo Molnar
2008-02-21 21:12 ` [PATCH 0/2] onlining cpus can break lockdep Ingo Molnar
2008-02-21 21:17 ` Glauber Costa [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=47BDEA82.8050508@redhat.com \
--to=gcosta@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pzijlstr@redhat.com \
/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.