All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@parallels.com>
To: Mahesh Bandewar <maheshb@google.com>
Cc: netdev <netdev@vger.kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Maciej Zenczykowski <maze@google.com>,
	Laurent Chavey <chavey@google.com>,
	Tim Hockin <thockin@google.com>,
	David Miller <davem@davemloft.net>,
	Brandon Philips <brandon.philips@coreos.com>
Subject: Re: [PATCH net-next 1/1] ipvlan: Initial check-in of the IPVLAN driver.
Date: Thu, 13 Nov 2014 19:57:50 +0400	[thread overview]
Message-ID: <5464D4FE.4060006@parallels.com> (raw)
In-Reply-To: <CAF2d9jjmFymJdZmnfDCCUTRSSm-63RPaEFdB3TeYOq9S3jcPOA@mail.gmail.com>


>> Maybe introduce some "lock" call for ipvlan device after which no new IP addresses
>> can be assigned? And the configuration would look like
>>
>> 1. create ipvlan
>> 2. move to proper net namespace
>> 3. add addresses
>> 4. lock
>>
>> ?
> Yes. Exporting this "locked" property on the master device so that it
> can be controlled from masters' net-ns. Only thing we have to ensure
> is that both possibilities are allowed i.e. trusted ns where config do
> not need to be locked as well as untrusted/hostile ns where one can
> lock it down. However this is a future enhancement and if your
> implementation idea is different than this concept; we can discuss it
> at the time of implementation.

Sure. It's not a wish for the very first version of the set, it can
be added later.

Thanks,
Pavel

  reply	other threads:[~2014-11-13 16:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 22:29 [PATCH net-next 1/1] ipvlan: Initial check-in of the IPVLAN driver Mahesh Bandewar
2014-11-11 23:12 ` Cong Wang
2014-11-11 23:19   ` David Miller
2014-11-12  0:37     ` Cong Wang
2014-11-11 23:22   ` Hannes Frederic Sowa
2014-11-12  0:39     ` Cong Wang
2014-11-12  2:29       ` Eric Dumazet
2014-11-12  2:46       ` Mahesh Bandewar
2014-11-11 23:28 ` Eric Dumazet
2014-11-12 23:36   ` Mahesh Bandewar
2014-11-12 16:11 ` Pavel Emelyanov
2014-11-12 23:56   ` Mahesh Bandewar
2014-11-13 11:07     ` Pavel Emelyanov
2014-11-13 16:50       ` Mahesh Bandewar
2014-11-13 15:57         ` Pavel Emelyanov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-13 23:25 Alexei Starovoitov
2014-11-14  5:47 ` Mahesh Bandewar

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=5464D4FE.4060006@parallels.com \
    --to=xemul@parallels.com \
    --cc=brandon.philips@coreos.com \
    --cc=chavey@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=maheshb@google.com \
    --cc=maze@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=thockin@google.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.