From: ebiederm@xmission.com (Eric W. Biederman)
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Netdev <netdev@vger.kernel.org>, Thomas Graf <tgraf@suug.ch>,
"Eric W. Biederman" <ebiederm@aristanetworks.com>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH] genetlink: make netns aware
Date: Wed, 17 Jun 2009 14:19:01 -0700 [thread overview]
Message-ID: <m18wjqwoca.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1245267218.31588.41.camel@johannes.local> (Johannes Berg's message of "Wed\, 17 Jun 2009 21\:33\:38 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> This makes generic netlink network namespace aware.
> No actual generic netlink families are made namespace
> aware, they need to be checked one by one and then
> set the family->netnsok member to true.
Nothing at first glance looks wrong.
Most of these genetlink things are network related so making it
network namespace aware makes sense.
My impression had been that genetlink was mostly not network related
and I would have to solve the other hard problem of how to filter
sockets based on other namespaces. I guess that can be delayed for
a while longer.
Eric
next prev parent reply other threads:[~2009-06-17 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 19:33 [PATCH] genetlink: make netns aware Johannes Berg
2009-06-17 21:19 ` Eric W. Biederman [this message]
2009-06-17 21:37 ` Johannes Berg
2009-06-17 21:49 ` Eric W. Biederman
2009-06-17 21:54 ` Johannes Berg
2009-06-17 21:26 ` Johannes Berg
2009-06-18 2:10 ` Brian Haley
2009-06-18 2:16 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2009-06-18 11:16 Johannes Berg
2009-06-19 1:12 ` Johannes Berg
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=m18wjqwoca.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=adobriyan@gmail.com \
--cc=ebiederm@aristanetworks.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).