From: ebiederm@xmission.com (Eric W. Biederman)
To: Pavel Emelyanov <xemul@parallels.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 1/2] net: Allow to create links with given ifindex
Date: Mon, 30 Jul 2012 03:56:47 -0700 [thread overview]
Message-ID: <87fw89h5zk.fsf@xmission.com> (raw)
In-Reply-To: <87pq7dh6b2.fsf@xmission.com> (Eric W. Biederman's message of "Mon, 30 Jul 2012 03:49:53 -0700")
ebiederm@xmission.com (Eric W. Biederman) writes:
> Pavel Emelyanov <xemul@parallels.com> writes:
>
>> Currently the RTM_NEWLINK results in -EOPNOTSUPP if the ifinfomsg->ifi_index
>> is not zero. I propose to allow requesting ifindices on link creation. This
>> is required by the checkpoint-restore to correctly restore a net namespace
>> (i.e. -- a container). The question what to do with pre-created devices such
>> as lo or sit fbdev is open, but for manually created devices this can be
>> solved by this patch.
>
> Have you walked through and found the locations where we still rely on
> ifindex being globally unique?
>
> Last time I was working in this area there were serveral places where
> things were indexed by just the interface index.
If it is really safe to make ifindex per network namespace at this
point you can make dev_new_ifindex have a per network namespace base
counter, and that will fix your problems with the loopback device.
Unless you have done the work to root out the last of dependencies on
ifindex being globally unique I think you will run into some operational
problems.
Eric
next prev parent reply other threads:[~2012-07-30 10:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 4:34 [PATCH 1/2] net: Allow to create links with given ifindex Pavel Emelyanov
2012-07-30 4:36 ` [PATCH 2/2] veth: Allow to create peer link " Pavel Emelyanov
2012-07-30 10:49 ` [PATCH 1/2] net: Allow to create links " Eric W. Biederman
2012-07-30 10:56 ` Eric W. Biederman [this message]
2012-07-31 9:03 ` Pavel Emelyanov
2012-07-31 11:58 ` Eric W. Biederman
2012-07-31 13:30 ` Pavel Emelyanov
2012-08-02 10:28 ` Eric Dumazet
2012-08-02 11:09 ` Eric W. Biederman
2012-08-02 23:37 ` David Miller
2012-08-02 23:26 ` David Miller
2012-08-03 5:45 ` Eric Dumazet
2012-08-03 5:51 ` Eric Dumazet
2012-08-03 23:56 ` David Miller
2012-08-04 7:10 ` Eric Dumazet
2012-08-04 8:25 ` David Miller
2012-07-30 11:51 ` Eric Dumazet
2012-07-30 12:33 ` Eric W. Biederman
2012-07-31 9:06 ` Pavel Emelyanov
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=87fw89h5zk.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xemul@parallels.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.