From: Andi Kleen <andi@firstfloor.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Greg KH <greg@kroah.com>,
chris.mason@oracle.com
Subject: Re: [patch 0/2] object debugging infrastructure
Date: Mon, 03 Mar 2008 13:42:40 +0100 [thread overview]
Message-ID: <p73ir046ksf.fsf@bingen.suse.de> (raw)
In-Reply-To: <20080301100019.640027768@linutronix.de> (Thomas Gleixner's message of "Sat\, 01 Mar 2008 10\:24\:52 -0000")
Thomas Gleixner <tglx@linutronix.de> writes:
>
> 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 providing additional checks
> whenever kernel memory is freed.
Nice idea to make this generic.
If you push this it would be also good to consider some variant
of the "crasher" code that is in SUSE Kernels to include with it.
It was originally written by Chris Mason and it also makes it easier
to stabilize such bugs. The basic idea is that a background thread
allocates lots of slabs and pages always poisons them and checks them
in the background. If someone corrupts memory that is noticed earlier
then
Basically it extends what your patchkit is doing to free memory too.
Chris' old patch:
http://firstfloor.org/~andi/crasher-26.diff
(various variants of that have existed over time)
-Andi
prev parent reply other threads:[~2008-03-03 12:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 10:24 [patch 0/2] object debugging infrastructure Thomas Gleixner
2008-03-01 10:24 ` [patch 1/2] infrastructure to debug (dynamic) objects Thomas Gleixner
2008-03-01 10:51 ` Andrew Morton
2008-03-01 11:44 ` Thomas Gleixner
2008-03-01 22:42 ` Peter Zijlstra
2008-03-02 10:06 ` Thomas Gleixner
2008-03-01 10:25 ` [patch 2/2] add timer specific object debugging code Thomas Gleixner
2008-03-02 5:20 ` [patch 0/2] object debugging infrastructure Greg KH
2008-03-02 9:54 ` Thomas Gleixner
2008-03-03 12:42 ` Andi Kleen [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=p73ir046ksf.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).