[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 06 Jun 2012 10:43:23 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: gaofeng@...fujitsu.com
Cc: serge.hallyn@...onical.com, ebiederm@...ssion.com,
herbert@...dor.apana.org.au, steffen.klassert@...unet.com,
eric.dumazet@...il.com, netdev@...r.kernel.org,
containers@...ts.linux-foundation.org
Subject: Re: [PATCH net-next v2 1/2] inetpeer: add namespace support for
inetpeer
From: Gao feng <gaofeng@...fujitsu.com>
Date: Tue, 5 Jun 2012 15:52:17 +0800
> now inetpeer doesn't support namespace,the information will
> be leaking across namespace.
>
> this patch move the global vars v4_peers and v6_peers to
> netns_ipv4 and netns_ipv6 as a field peers.
>
> add struct pernet_operations inetpeer_ops to initial pernet
> inetpeer data.
>
> and change family_to_base and inet_getpeer to support namespace.
>
> Signed-off-by: Gao feng <gaofeng@...fujitsu.com>
As stated yesterday we have to move the inetpeer tree roots into
the FIB rule entries to fix other bugs, and that as a result will
transparently fix this problem too.
So I'm dropping these two patches and will work on the mentioned
approach to this fix.
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
Powered by blists - more mailing lists