netdev - Re: net-next: NULL pointer dereference on adding a net namespace and a system freeze

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1394459069.3607.8.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Mon, 10 Mar 2014 06:44:29 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Fan Du <fan.du@...driver.com>
Cc:	Jakub Kicinski <moorray3@...pl>, netdev@...r.kernel.org,
	Steffen Klassert <steffen.klassert@...unet.com>
Subject: Re: net-next: NULL pointer dereference on adding a net namespace
 and a system freeze

On Mon, 2014-03-10 at 14:51 +0800, Fan Du wrote:

> Sometimes network activity only on netns could trigger bugs like memory leakage,
> using per-netns kmem_cache could help to identify which netns to be blamed.
> 
> Anyway if this is inappropriate, let's make it global as you did below.

But you forgot to kmem_cache_destroy() the cache at netns removal, so
this also is a leak ;)



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html