On 26/05/06, Ingo Molnar <[email protected]> wrote:
All in one, i'm very much in favor of adding kmemleak to the upstream
kernel, once it gets clean enough and has seen some exposure on -mm.
I cleaned it and also tested it on SMP. I need to run a few more tests
on x86 (as I mainly work on ARM) and release a new version this
weekend.
A problem I'm facing (also because I'm not familiar with the other
architectures) is detecting the effective stack boundaries of the
threads running or waiting in kernel mode. Scanning the whole stack
(8K) hides some possible leaks (because of no longer used local
variables) and not scanning the list at all can lead to false
positives. I would need to investigate this a bit more.
--
Catalin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
