From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>
Subject: [patch 0/5] object debugging infrastructure V2
Date: Wed, 05 Mar 2008 16:03:33 -0000 [thread overview]
Message-ID: <20080305154829.185609547@linutronix.de> (raw)
This is version 2 of the object debugging infrastructure. Changes
versus V1:
- review comments processed:
- multiplexing interfaces replaced
- object type is determined by a caller provided pointer to
a debug structure which replaces the object type identifier
-> No changes to the core code for new users
- new debug state "destroyed" (kobject wishlist)
- various cleanups
- complete detachment of the tracker object from the real object
(no change to the real objects data structure necessary anymore)
- improved robustness (object memory management, oom cleanup)
- full set of self tests
- debugfs statistics
- docbook documentation
Thanks,
tglx
--
next reply other threads:[~2008-03-05 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 16:03 Thomas Gleixner [this message]
2008-03-05 16:03 ` [patch 1/5] vmalloc: do not check for freed locks on user maps Thomas Gleixner
2008-03-05 16:28 ` Nick Piggin
2008-03-05 17:20 ` Thomas Gleixner
2008-03-05 22:56 ` Nick Piggin
2008-03-05 23:31 ` Thomas Gleixner
2008-03-06 2:34 ` Nick Piggin
2008-03-05 16:03 ` [patch 2/5] slab: add a flag to prevent debug_free checks on a kmem_cache Thomas Gleixner
2008-03-05 16:03 ` [patch 3/5] infrastructure to debug (dynamic) objects Thomas Gleixner
2008-03-05 16:04 ` [patch 4/5] debugobjects: add documentation Thomas Gleixner
2008-03-10 20:13 ` Randy Dunlap
2008-03-21 14:25 ` Thomas Gleixner
2008-03-05 16:04 ` [patch 5/5] debugobjects: add timer specific object debugging code Thomas Gleixner
2008-03-05 20:14 ` Thomas Gleixner
2008-03-05 18:53 ` [patch 0/5] object debugging infrastructure V2 Greg KH
2008-03-06 1:48 ` Greg KH
2008-03-06 7:54 ` 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=20080305154829.185609547@linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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