Messages in this thread |  | | | Date | Sat, 1 Mar 2008 21:20:07 -0800 | | From | Greg KH <> | | Subject | Re: [patch 0/2] object debugging infrastructure | |
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.
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.
If so, I'll gladly add this to the kobjects to help with issues there.
thanks,
greg k-h
|  |