Messages in this thread | | | Date | Thu, 29 Sep 2011 09:08:47 -0500 (CDT) | From | Christoph Lameter <> | Subject | Re: Question about memory leak detector giving false positive report for net/core/flow.c |
| |
On Wed, 28 Sep 2011, Catalin Marinas wrote:
> I tried this but it's tricky. The problem is that the percpu pointer > returned by alloc_percpu() does not directly point to the per-cpu chunks > and kmemleak would report most percpu allocations as leaks. So far the > workaround is to simply mark the alloc_percpu() objects as never leaking > and at least we avoid false positives in other areas. See the patch > below (note that you have to increase the CONFIG_KMEMLEAK_EARLY_LOG_SIZE > as there are many alloc_percpu() calls before kmemleak is fully > initialised):
Seems that kernel.org is out and so tejon wont be seeing these.
| |