Re: [PATCH 2.6.17-rc6 7/9] Remove some of the kmemleak false positives

[Ingo Molnar <mingo@elte.hu>]

* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> This seems pretty over-engineered.  I wouldn't go this far unless 
> you're actually seeing performance/correctness problems, and a simple 
> with/without pointers flag isn't enough.  It also doesn't address the 
> most troublesome source of false pointers: stacks.  There is all sorts 
> of junk lying around on stacks, and you can have an old dead pointer 
> sitting there pinning old dead memory for a long time.

in an earlier thread i suggested to not scan kernel stacks at all, but 
to delay the registration of new blocks to return-from-syscall time (via 
having a per-task list of newly allocated but not yet registered 
blocks). That way we dont get false positives for stuff that is on the 
kernel stack temporarily and then freed, and we correctly register newly 
allocated blocks as well.

	Ingo