From: ebiederm@xmission.com (Eric W. Biederman)
To: Steven Rostedt <rostedt@goodmis.org>
Cc: David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, viro@zeniv.linux.org.uk,
tixxdz@opendz.org
Subject: Re: [PATCH] net: Surpress kmemleak messages on sysctl paths
Date: Tue, 22 May 2012 08:41:17 -0600 [thread overview]
Message-ID: <878vgk1do2.fsf@xmission.com> (raw)
In-Reply-To: <1337647392.13348.14.camel@gandalf.stny.rr.com> (Steven Rostedt's message of "Mon, 21 May 2012 20:43:12 -0400")
Steven Rostedt <rostedt@goodmis.org> writes:
> The network code allocates ctl_table_headers that are used for the life
> of the kernel. These headers are registered and never unregistered. The
> head pointer is allocated and not referenced, as it never needs to be
> unregistered, and the kmemleak detector triggers these as false
> positives:
The fix for this should already be merged into Linus's tree from the
net-next tree for 3.5.
Eric
next prev parent reply other threads:[~2012-05-22 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 0:43 [PATCH] net: Surpress kmemleak messages on sysctl paths Steven Rostedt
2012-05-22 14:41 ` Eric W. Biederman [this message]
2012-05-22 14:51 ` Steven Rostedt
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=878vgk1do2.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tixxdz@opendz.org \
--cc=viro@zeniv.linux.org.uk \
/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