From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, greg@kroah.com,
randy.dunlap@oracle.com
Subject: Re: [patch 2/5] infrastructure to debug (dynamic) objects
Date: Mon, 24 Mar 2008 13:04:54 -0700 [thread overview]
Message-ID: <20080324130454.ced60108.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080321200321.650649403@linutronix.de>
On Fri, 21 Mar 2008 20:26:18 -0000
Thomas Gleixner <tglx@linutronix.de> wrote:
> The debugobjects core code keeps track of operations on static and
> dynamic objects by inserting them into a hashed list and sanity
> checking them on object operations and provides additional checks
> whenever kernel memory is freed.
Prime candidates for conversion to this interface are locks: spinlocks,
rwlocks, mutexes, etc.
a) it'd be interesting to get that done, as a proof-of-usefulness thing.
b) but this code internally uses spinlocks. Will it explode?
also list_heads and hlists. But
a) that might be a bit redundant against the custome debugging which lists
already have and
b) this code uses lists and hlists internally?
next prev parent reply other threads:[~2008-03-24 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 20:26 [patch 0/5] debugobject infrastructure V3 Thomas Gleixner
2008-03-21 20:26 ` [patch 1/5] slab: add a flag to prevent debug_free checks on a kmem_cache Thomas Gleixner
2008-03-21 20:26 ` [patch 2/5] infrastructure to debug (dynamic) objects Thomas Gleixner
2008-03-21 20:55 ` Randy Dunlap
2008-03-21 21:24 ` Thomas Gleixner
2008-03-24 20:04 ` Andrew Morton [this message]
2008-03-25 8:19 ` Thomas Gleixner
2008-03-26 23:23 ` Thomas Gleixner
2008-03-21 20:26 ` [patch 3/5] debugobjects: add documentation Thomas Gleixner
2008-03-21 20:26 ` [patch 4/5] debugobjects: add timer specific object debugging code Thomas Gleixner
2008-04-26 16:28 ` Andrew Morton
2008-03-21 20:26 ` [patch 5/5] add hrtimer specific debugobjects code Thomas Gleixner
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=20080324130454.ced60108.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--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 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.