From: "Daniel J Blueman" <daniel.blueman@gmail.com>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: "Christoph Lameter" <clameter@sgi.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@elte.hu>,
"Pekka Enberg" <penberg@cs.helsinki.fi>
Subject: Re: 2.6.26-rc5: SLUB debug, lockdep warning...
Date: Sun, 15 Jun 2008 00:50:24 +0100 [thread overview]
Message-ID: <6278d2220806141650t520027ccw46d4ee936d101501@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0806141423m18e35f29qb736d44460d70785@mail.gmail.com>
On Sat, Jun 14, 2008 at 10:23 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> On Sat, Jun 14, 2008 at 12:54 PM, Daniel J Blueman
> <daniel.blueman@gmail.com> wrote:
>> When enabling lockdep + SLUB debugging, I spotted this recursive
>> lock-acquisition warning [1] when booting, however it doesn't always
>> pop out.
>
> This seems to be the work of
>
> commit 3ac7fe5a4aab409bd5674d0b070bce97f9d20872
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Wed Apr 30 00:55:01 2008 -0700
>
> infrastructure to debug (dynamic) objects
>
> ...which by the way changed SLUB without any SOBs from any of the SLUB
> maintainers?
> Anyway, adding some Ccs.
Thanks for the detective work Vegard!
>> Let me know if you need further information etc.
>
> Exact kernel version and your config file would be useful (please post
> it online somewhere if possible). Thanks!
2.6.26-rc5 mainline, x86-64 dual-core with maximal debug, running
stock Ubuntu 8.04 desktop, NFSv4 home; seems to trigger always with
nscd loading on boot. Config at:
http://quora.org/slub-lockdep-config
--
Daniel J Blueman
prev parent reply other threads:[~2008-06-14 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 10:54 Daniel J Blueman
2008-06-14 21:23 ` Vegard Nossum
2008-06-14 23:50 ` Daniel J Blueman [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=6278d2220806141650t520027ccw46d4ee936d101501@mail.gmail.com \
--to=daniel.blueman@gmail.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®