Re: [PATCH] net: Surpress kmemleak messages on sysctl paths

2 messages, 2 authors, 2012-05-22 · open the first message on its own page

Re: [PATCH] net: Surpress kmemleak messages on sysctl paths

From: Eric W. Biederman <hidden>
Date: 2012-05-22 14:41:32

Steven Rostedt [off-list ref] 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

Re: [PATCH] net: Surpress kmemleak messages on sysctl paths

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2012-05-22 14:51:23

On Tue, 2012-05-22 at 08:41 -0600, Eric W. Biederman wrote:
Steven Rostedt [off-list ref] writes:
quoted
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.
Ah, I didn't look at net-next. I just looked at 3.4 and didn't see
anything. If that's the case, simply ignore :-)

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help