From: ebiederm@xmission.com (Eric W. Biederman)
To: minyard@acm.org
Cc: Corey Minyard <cminyard@mvista.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] namespace: Add an identifier to the namespace file
Date: Wed, 26 Sep 2012 19:30:01 -0700 [thread overview]
Message-ID: <87sja4kxjq.fsf@xmission.com> (raw)
In-Reply-To: <5063A6DD.9070202@acm.org> (Corey Minyard's message of "Wed, 26 Sep 2012 20:07:41 -0500")
Corey Minyard <tcminyard@gmail.com> writes:
> On 09/26/2012 07:48 PM, Eric W. Biederman wrote:
>> For netfilter or any other interface what should happen is that a file
>> descriptor is passed in and the network namespace is derived from the
>> file descriptor.
>>
>> Given that netfilter is per network namespace I'm not certain how
>> filtering per network namespace would make sense.
>>
>> When I have poked my nose into netfilter I have had the hard problem
>> that I have not figured out how to translate the parameters supplied
>> by userspace into a more appropriate in kernel form, so I'm not certain
>> how to implement passing a file descriptor into netfilter efficiently.
>
> Yeah, that's kind of where I am stuck, too. netfilter used to be global,
> so if it's not, this may be a "You can't do that any more".
I expect this will come down closer to you can't do it that way anymore.
Eric
prev parent reply other threads:[~2012-09-27 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1348681743-16129-1-git-send-email-minyard@acm.org>
[not found] ` <87lifwmib4.fsf@xmission.com>
[not found] ` <50639F4F.8010404@mvista.com>
2012-09-27 0:48 ` [PATCH] namespace: Add an identifier to the namespace file Eric W. Biederman
2012-09-27 1:07 ` Corey Minyard
2012-09-27 2:30 ` Eric W. Biederman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sja4kxjq.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=cminyard@mvista.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.