[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140513083945.062de6c3@nehalam.linuxnetplumber.net>
Date: Tue, 13 May 2014 08:39:45 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: netdev@...r.kernel.org
Subject: Problem with iflink in netns
There have been a couple of bugzilla reports already about cases where a macvlan
or vlan is moved into another namespace. In these cases the parent device ifindex (iflink)
is no longer valid.
Normally it is not a big issue, until another device is created using the ifindex
of the parent
Does anyone have a suggested fix? Marking iflink as 0 won't work then the devices no
longer appear as slaves. Another possibility would be to make block creation of device
where ifindex matches existing iflink of other devices; but this would slow down device
creation.
The bugs come in as ip command bugs, but obviously the issue is in the kernel.
https://bugzilla.kernel.org/show_bug.cgi?id=66691
https://bugzilla.kernel.org/show_bug.cgi?id=75911
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists