[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061122164154.GB17378@sergelap.austin.ibm.com>
Date: Wed, 22 Nov 2006 10:41:54 -0600
From: "Serge E. Hallyn" <serue@...ibm.com>
To: Cedric Le Goater <clg@...ibm.com>
Cc: Dmitry Mishin <dim@...nvz.org>,
Daniel Lezcano <dlezcano@...ibm.com>,
Kirill Korotaev <dev@...ru>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>,
Herbert Poetzl <herbert@...hfloor.at>,
"Eric W. Biederman" <ebiederm@...ssion.com>, netdev@...r.kernel.org
Subject: Re: [patch -mm] net namespace: empty framework
Quoting Cedric Le Goater (clg@...ibm.com):
> Hello,
>
> Dmitry Mishin wrote:
>
> > This patch looks acceptable for us.
>
> good. shall we merge it then ? see comment below.
>
> > BTW, Daniel, we agreed to be based on the Andrey's patchset. I do not see a
> > reason, why Cedric force us to make some unnecessary work and move existent
> > patchset over his interface.
>
> yeah it's a bit different from andrey's but not that much and it's more in
Where is Andrey's patch?
> the spirit of uts and ipc namespace (and user namespace if that reaches the
> kernel one day :) so that's why i made the small changes.
I agree the namespace frameworks should be consistent, but i don't know
whether Andrey's is or not. I'd like to have the framework included so
we reduce the number of silly rewrites due to clone flag collisions etc.
>
> It also helping the nsproxy/namespace syscalls to have a similar interface
> to manipulate namespaces. who knows, soon we might be able to have a 'struct
> namespace' with a ops field to define new namespace types ?
>
> I can also send a empty framework for user namespace ;)
Please do - then I'll rebase the patchset I sent to the containes list
onto your patch, and resubmit the whole userns.
-serge
-
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