netdev - Re: network namespace and kernel bind issue

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.LFD.2.00.1210020910010.1642@ja.ssi.bg>
Date:	Tue, 2 Oct 2012 09:15:46 +0300 (EEST)
From:	Julian Anastasov <ja@....bg>
To:	Stephen Hemminger <shemminger@...tta.com>
cc:	"Eric W. Biederman" <ebiederm@...ssion.com>, netdev@...r.kernel.org
Subject: Re: network namespace and kernel bind issue

	Hello,

On Mon, 1 Oct 2012, Stephen Hemminger wrote:

> The problem was vxlan wasn't doing sk_change_net on the created socket.
> 
> I'm testing that fix.
> 
> The long term fix is to change sock_create_kern() to take a 'struct net'
> argument. This would avoid the trap of having to change the namespace.
> Also several places using __sock_create() could use it.
> 
> L2TP still looks to have several namespace related issues.

	There should be also .netnsok = true in l2tp_nl_family
as final step.

Regards

--
Julian Anastasov <ja@....bg>
--
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