From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Roland Dreier <roland@topspin.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Proposal] DEBUG_SLAB should select DEBUG_SPINLOCK
Date: Fri, 28 May 2004 12:42:28 -0700 [thread overview]
Message-ID: <20040528124228.105ebcbb.rddunlap@osdl.org> (raw)
In-Reply-To: <528yfc72u8.fsf@topspin.com>
On 28 May 2004 12:45:35 -0700 Roland Dreier wrote:
| I recently had a rather amusing debugging session. I developed some
| code that worked fine on my test kernel, which had CONFIG_DEBUG_SLAB
| turned on. However, as soon as I moved to a kernel without slab
| debugging to do some benchmarks, I started getting lockups. It turns
| out that I had a spinlock in my data structure that I forgot to
| initialize but the poisoning from slab debugging had taken care of
| initializing it for me. I didn't catch this during development
| because I had left CONFIG_DEBUG_SPINLOCK off.
|
| Fortunately (for my sanity) I was able to diagnose this pretty quickly
| with the help of the NMI oopser. However, for other developers' sake,
| I think it might make sense to add
|
| select DEBUG_SPINLOCK
|
| to the DEBUG_SLAB stanza of Kconfig.
|
| I'm not posting a patch because I wanted to find out the status of
| Randy Dunlap's patch that consolidates the debugging options. Is that
| patch going to be merged, in someone's tree somewhere, dropped, or what?
Andrew asked me to delay it until 2.6.6, which I did.
Sent that, but not merged.
I will be rediffing it and resending it again for 2.6.7 and
probably some intermediate kernels if that's what it takes.
| If the consensus is that we don't want to do this anyway, that's
| fine. I mostly wanted to share this bug, which amused me.
--
~Randy
next prev parent reply other threads:[~2004-05-28 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 19:45 [Proposal] DEBUG_SLAB should select DEBUG_SPINLOCK Roland Dreier
2004-05-28 19:42 ` Randy.Dunlap [this message]
2004-05-28 19:54 ` Roland Dreier
2004-05-28 20:00 ` Randy.Dunlap
2004-05-28 20:35 ` Roland Dreier
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=20040528124228.105ebcbb.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.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