Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, johannes.berg@intel.com
Subject: Re: [PATCH] netlink/genetlink: pass network namespace to bind/unbind
Date: Sat, 27 Dec 2014 03:08:05 -0500 (EST)	[thread overview]
Message-ID: <20141227.030805.2148263042773135498.davem@davemloft.net> (raw)
In-Reply-To: <1419364806-8753-1-git-send-email-johannes@sipsolutions.net>

From: Johannes Berg <johannes@sipsolutions.net>
Date: Tue, 23 Dec 2014 21:00:06 +0100

> From: Johannes Berg <johannes.berg@intel.com>
> 
> Netlink families can exist in multiple namespaces, and for the most
> part multicast subscriptions are per network namespace. Thus it only
> makes sense to have bind/unbind notifications per network namespace.
> 
> To achieve this, pass the network namespace of a given client socket
> to the bind/unbind functions.
> 
> Also do this in generic netlink, and there also make sure that any
> bind for multicast groups that only exist in init_net is rejected.
> This isn't really a problem if it is accepted since a client in a
> different namespace will never receive any notifications from such
> a group, but it can confuse the family if not rejected (it's also
> possible to silently (without telling the family) accept it, but it
> would also have to be ignored on unbind so families that take any
> kind of action on bind/unbind won't do unnecessary work for invalid
> clients like that.
> 
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>

Applied, thanks Johannes.

      reply	other threads:[~2014-12-27 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 20:00 [PATCH] netlink/genetlink: pass network namespace to bind/unbind Johannes Berg
2014-12-27  8:08 ` David Miller [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=20141227.030805.2148263042773135498.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=netdev@vger.kernel.org \
    /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