From: Catalin Marinas <catalin.marinas@arm.com>
To: Christoph Lameter <cl@gentwo.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Huajun Li <huajun.li.lee@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: Question about memory leak detector giving false positive report for net/core/flow.c
Date: Thu, 29 Sep 2011 15:18:10 +0100 [thread overview]
Message-ID: <20110929141809.GD32023@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1109290907450.9382@router.home>
On Thu, Sep 29, 2011 at 03:08:47PM +0100, Christoph Lameter wrote:
> 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.
That's ok, I don't aim this at the upcoming merging window. I don't have
an alternative email address for him.
--
Catalin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-09-29 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 15:17 Question about memory leak detector giving false positive report for net/core/flow.c Huajun Li
2011-09-26 16:32 ` Eric Dumazet
2011-09-26 16:50 ` Catalin Marinas
2011-09-26 19:46 ` Eric Dumazet
2011-09-27 5:29 ` Huajun Li
2011-09-27 5:55 ` Eric Dumazet
2011-09-27 16:58 ` Catalin Marinas
2011-09-27 17:01 ` Catalin Marinas
2011-09-28 17:23 ` Catalin Marinas
2011-09-29 14:08 ` Christoph Lameter
2011-09-29 14:18 ` Catalin Marinas [this message]
2011-09-29 19:07 ` Tejun Heo
2011-09-27 5:27 ` Huajun Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110929141809.GD32023@e102109-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=eric.dumazet@gmail.com \
--cc=huajun.li.lee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).