[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090413071111.GA7085@x200.localdomain>
Date: Mon, 13 Apr 2009 11:11:11 +0400
From: Alexey Dobriyan <adobriyan@...il.com>
To: "Serge E. Hallyn" <serue@...ibm.com>
Cc: akpm@...ux-foundation.org, containers@...ts.linux-foundation.org,
xemul@...allels.com, dave@...ux.vnet.ibm.com, mingo@...e.hu,
orenl@...columbia.edu, hch@...radead.org,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 07/30] netns: extract net_create()
On Fri, Apr 10, 2009 at 05:56:36PM -0500, Serge E. Hallyn wrote:
> Quoting Alexey Dobriyan (adobriyan@...il.com):
> > net_create() will be used by C/R code to create fresh netns on restart.
> >
> > Signed-off-by: Alexey Dobriyan <adobriyan@...il.com>
>
> Acked-by: Serge Hallyn <serue@...ibm.com>
>
> Although this ends up making a new assumption that setup_net(), and
> therefore the pernet_ops->init() functions, do not return error > 0.
> There's nothing actually stopping that (outside of code review, but
> there appears to be no comment anywhere saying that's uncooth).
>
> If it returns > 0, then we return the ns as though it were valid, but
> don't add it to the list of namespaces... Do we care?
I think, no.
Recalling all the code put under netns changes, ->init hooks were put
under 0/-E convention. For sure, my changes in netns xtables,
conntracking and xfrm were definitely under it.
> > -struct net *copy_net_ns(unsigned long flags, struct net *old_net)
> > +struct net *net_create(void)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists