From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <greg@kroah.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 0/2] object debugging infrastructure
Date: Sun, 2 Mar 2008 10:54:58 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0803021051020.11084@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080302052007.GA24573@kroah.com>
On Sat, 1 Mar 2008, Greg KH wrote:
> On Sat, Mar 01, 2008 at 10:24:52AM -0000, Thomas Gleixner wrote:
> > We can see an ever repeating problem pattern with objects of any kind in
> > the kernel:
> >
> > 1) free of active objects
> > 2) reinitialization of active objects
>
> Ah, this looks nice. For kobjects I would like to track the above, as
> well as:
> - use of initialized objects
> - use of "freed" objects
> - objects that are never destroyed, yet the code controlling
> them thinks they are.
>
> I say "freed" as sometimes kobjects are in static structures and are not
> in memory that ends up being kfree() so slab poisoning doesn't help.
Good point. I try to come up with the infrastructure for that.
> Do you think that would be able to worked into this framework? At first
> glance, it seems like it would be easy to add, but would like to make
> sure.
Yes, that should be possible
> If so, I'll gladly add this to the kobjects to help with issues there.
kobjects came to my mind as well, when I was thinking about possible
use cases.
Thanks,
tglx
next prev parent reply other threads:[~2008-03-02 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 10:24 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 [this message]
2008-03-03 12:42 ` Andi Kleen
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=alpine.LFD.1.00.0803021051020.11084@apollo.tec.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 \
/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®