From: Andrew Morton <akpm@osdl.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: sekharan@us.ibm.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org, nagar@watson.ibm.com,
balbir@in.ibm.com, arjan@infradead.org
Subject: Re: [patch] lockdep: more annotations for mm/slab.c
Date: Thu, 13 Jul 2006 02:08:01 -0700 [thread overview]
Message-ID: <20060713020801.44b99061.akpm@osdl.org> (raw)
In-Reply-To: <20060713084613.GA7177@elte.hu>
On Thu, 13 Jul 2006 10:46:13 +0200
Ingo Molnar <mingo@elte.hu> wrote:
> the SLAB code can hold multiple slab locks at once,
> for example at:
>
> [<c0105dd5>] show_trace+0xd/0x10
> [<c0105def>] dump_stack+0x17/0x1c
> [<c014182e>] __lock_acquire+0x7ab/0xa0e
> [<c0141d6e>] lock_acquire+0x5e/0x80
> [<c10b0d8e>] _spin_lock_nested+0x26/0x37
> [<c017178b>] __cache_free+0x30d/0x3d2
> [<c0171200>] slab_destroy+0xfd/0x11d
> [<c0171360>] free_block+0x140/0x17d
> [<c01717dd>] __cache_free+0x35f/0x3d2
> [<c01718cd>] kfree+0x7d/0x9a
> [<c0127889>] free_task+0xe/0x24
> [<c0127ee8>] __put_task_struct+0xc2/0xc7
> [<c012bc8f>] delayed_put_task_struct+0x1e/0x20
> [<c0139d94>] __rcu_process_callbacks+0xff/0x15d
> [<c0139e1a>] rcu_process_callbacks+0x28/0x40
> [<c012f125>] tasklet_action+0x6e/0xd1
> [<c012f2c7>] __do_softirq+0x6e/0xec
> [<c01061b7>] do_softirq+0x61/0xc7
>
> so add the 'nested' parameter to the affected functions.
>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> mm/slab.c | 45 +++++++++++++++++++++++++--------------------
geeze, what fuss. Can't we just tell lockdep "the locking here is correct,
so buzz off"?
next prev parent reply other threads:[~2006-07-13 9:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 3:59 Random panics seen in 2.6.18-rc1 Chandra Seetharaman
2006-07-13 7:12 ` Ingo Molnar
2006-07-13 7:28 ` Andrew Morton
2006-07-13 7:26 ` Ingo Molnar
2006-07-13 7:44 ` Andrew Morton
2006-07-13 7:46 ` Ingo Molnar
2006-07-13 8:49 ` Ingo Molnar
2006-07-13 8:42 ` Ingo Molnar
2006-07-13 8:46 ` [patch] lockdep: more annotations for mm/slab.c Ingo Molnar
2006-07-13 9:08 ` Andrew Morton [this message]
2006-07-13 9:18 ` Ingo Molnar
2006-07-13 10:44 ` Arjan van de Ven
2006-07-13 10:58 ` Arjan van de Ven
2006-07-13 12:44 ` [patch] lockdep: undo mm/slab.c annotation Ingo Molnar
2006-07-13 12:46 ` [patch] lockdep: annotate mm/slab.c Ingo Molnar
2006-07-13 15:45 ` Pekka Enberg
2006-07-13 19:55 ` Ingo Molnar
2006-07-13 15:58 ` Pekka Enberg
2006-07-13 18:56 ` Linus Torvalds
2006-07-13 19:21 ` Arjan van de Ven
2006-07-13 22:27 ` Christoph Lameter
2006-07-13 23:08 ` Alok kataria
2006-07-13 22:51 ` Christoph Lameter
2006-07-13 23:16 ` Andrew Morton
2006-07-14 2:29 ` Christoph Lameter
2006-07-14 2:46 ` Christoph Lameter
2006-07-14 3:02 ` Andrew Morton
2006-07-14 3:35 ` Christoph Lameter
2006-07-14 3:45 ` Christoph Lameter
2006-07-14 16:48 ` Alok kataria
2006-07-14 2:54 ` Andrew Morton
2006-07-14 2:59 ` Christoph Lameter
2006-07-13 19:32 ` Ingo Molnar
2006-07-13 18:50 ` Linus Torvalds
2006-07-13 19:06 ` Arjan van de Ven
2006-07-13 19:21 ` Linus Torvalds
2006-07-13 19:26 ` Arjan van de Ven
2006-07-13 19:17 ` Ingo Molnar
2006-07-13 19:19 ` Ingo Molnar
2006-07-13 21:30 ` Andrew Morton
2006-07-13 13:51 ` Random panics seen in 2.6.18-rc1 Chandra Seetharaman
2006-07-13 16:05 ` Chandra Seetharaman
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=20060713020801.44b99061.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nagar@watson.ibm.com \
--cc=sekharan@us.ibm.com \
--cc=torvalds@osdl.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
Powered by JetHome