netdev - Re: [PATCH net-next] net: kernel socket should be released in init

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] [day] [month] [year] [list]

Date:	Mon, 16 Mar 2015 16:25:25 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	ying.xue@...driver.com
Cc:	netdev@...r.kernel.org, edumazet@...gle.com, ebiederm@...ssion.com
Subject: Re: [PATCH net-next] net: kernel socket should be released in
 init_net namespace

From: Ying Xue <ying.xue@...driver.com>
Date: Mon, 16 Mar 2015 18:19:12 +0800

> Creating a kernel socket with sock_create_kern() happens in "init_net"
> namespace, however, releasing it with sk_release_kernel() occurs in
> the current namespace which may be different with "init_net" namespace.
> Therefore, we should guarantee that the namespace in which a kernel
> socket is created is same as the socket is created.
> 
> Signed-off-by: Ying Xue <ying.xue@...driver.com>

Applied, thanks.
--
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