Re: kmemleak hexdump proposal

[Sergey Senozhatsky]

On (06/29/09 11:38), Catalin Marinas wrote:
> On Mon, 2009-06-29 at 13:19 +0300, Pekka Enberg wrote:
> > On Mon, 2009-06-29 at 13:19 +0300, Sergey Senozhatsky wrote:
> > > Well, it's not easy to come up with something strong. 
> > > I agree, that stack gives you almost all you need.
> > > 
> > > HEX dump can give you a _tip_ in case you're not sure. 
> > 
> > Don't get me wrong, I'm not against it in any way. If Catalin is
> > interested in merging this kind of functionality, go for it! You might
> > want to consider unconditionally enabling the hexdump. If the
> > information is valuable, we should print it all the time.
> 
> Though I prefer to do as much as possible in user space, 
Agreed. Good example is 'function filtering' ;)

> I think this feature would be useful.
> 
So, I'll continue my work. (given patch didn't even passed ./checkpatch.pl).
Ok?

> Anyway, I may not include it before the next merging window (when is
> actually the best time for new features). Currently, my main focus is on
> reducing the false positives.
Sure. No problems.

> 
> -- 
> Catalin
> 

	Sergey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/