[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHA+R7POE-X0Tbn6XEGSta=tDZQ_+EDg0ruSxy3qMFNm9Rd0oQ@mail.gmail.com>
Date: Thu, 7 May 2015 11:53:32 -0700
From: Cong Wang <cwang@...pensource.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Ying Xue <ying.xue@...driver.com>, netdev <netdev@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Pavel Emelyanov <xemul@...nvz.org>,
David Miller <davem@...emloft.net>,
Eric Dumazet <eric.dumazet@...il.com>, maxk@....qualcomm.com,
Stephen Hemminger <stephen@...workplumber.org>,
Thomas Graf <tgraf@...g.ch>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
Tom Herbert <tom@...bertland.com>,
James Chapman <jchapman@...alix.com>,
Erik Hugne <erik.hugne@...csson.com>, jon.maloy@...csson.com,
Simon Horman <horms@...ge.net.au>
Subject: Re: [RFC PATCH net-next 00/11] netns: don't switch namespace while
creating kernel sockets
On Thu, May 7, 2015 at 11:26 AM, Eric W. Biederman
<ebiederm@...ssion.com> wrote:
> Cong Wang <cwang@...pensource.com> writes:
>
>>
>> Why does this have to be so complicated? We can simply avoid
>> calling ops_init() by skipping those in cleanup_list, no?
>
> The problem is that there is a single list of methods to call and if you
> simply skip calling the initialization methods for a struct net and add
> yourself to the list cleanup_net will then call the cleanup methods
> without calling the cleanup methods.
If you mean pernet_list, ops->list has been already added before
for_each_net().
>
> Simply limiting new network namespace registrations to a point when
> network namespaces are not being registered or unregisted seems like
> the simplest way to achieve this effect.
>
Literally, any point before ops_init().
--
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