From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Daniel J Blueman" <daniel.blueman@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: Sat, 14 Jun 2008 23:23:35 +0200 [thread overview]
Message-ID: <19f34abd0806141423m18e35f29qb736d44460d70785@mail.gmail.com> (raw)
In-Reply-To: <6278d2220806140354i7f163086i6127664d8c2d88a9@mail.gmail.com>
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.
>
> 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!
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-06-14 21:32 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 [this message]
2008-06-14 23:50 ` Daniel J Blueman
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=19f34abd0806141423m18e35f29qb736d44460d70785@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=clameter@sgi.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=tglx@linutronix.de \
/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®