[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1ocjf1k9d.fsf@fess.ebiederm.org>
Date: Tue, 23 Feb 2010 17:43:10 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: hadi@...erus.ca
Cc: Daniel Lezcano <dlezcano@...ibm.com>,
Patrick McHardy <kaber@...sh.net>,
Linux Netdev List <netdev@...r.kernel.org>,
containers@...ts.linux-foundation.org,
Netfilter Development Mailinglist
<netfilter-devel@...r.kernel.org>,
Ben Greear <greearb@...delatech.com>
Subject: Re: RFC: netfilter: nf_conntrack: add support for "conntrack zones"
jamal <hadi@...erus.ca> writes:
> On Tue, 2010-02-23 at 12:00 -0800, Eric W. Biederman wrote:
>
>> That point of the mount to hold a persistent reference to the
>> namespace without using a process.
>>
>> The point of the of the to be written set_ns call is to change
>> the default network namespace of the process such that all future
>> open/bind/socket calls happen in the referenced network namespace.
>
> Ok, i like it ;-> Patches RSN? Let me if you want someone to test..
My target will be 2.6.35. There is an old prototype implementation
that hit the containers list and I think netdev a year or so ago.
>> The are a few stray places like sysfs where it is the mount point
>> not current->nsproxy->net_ns that will determine what we see.
>
> Is sysfs considered "usable enough" for namespaces?
Mine is ;) I had a bad cold and didn't get through all of the patches
this development cycle, just all the prereqs. I plan on getting that
final conversation started for as soon as 2.6.34-rc1 hits.
>> Attributes of the specific namespace?
>
> Well, example what is being un/shared etc.
Got it. Implementation wise I'm going to stash a pointer
to the namespace in a inode or super block, simple.
Eric
--
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