MIME-Version: 1.0
In-Reply-To: <49C9087C.5070907@trash.net>
References: <20090324154617.GA16332@auslistsprd01.us.dell.com>
	 <49C9087C.5070907@trash.net>
Date: Tue, 24 Mar 2009 17:28:33 +0100
Message-ID: <ac3eb2510903240928s6c42bc32pa0cd8a7f0e69b731@mail.gmail.com>
Subject: Re: Network Device Naming mechanism and policy
From: Kay Sievers <kay.sievers@vrfy.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Matt Domsch <Matt_Domsch@dell.com>, netdev@vger.kernel.org,
       linux-hotplug@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1775
Lines: 41

On Tue, Mar 24, 2009 at 17:21, Patrick McHardy <kaber@trash.net> wrote:
> Matt Domsch wrote:
>>
>> 2) udev may have rules to change the device names.  This is most often
>>   seen in the '70-persistent-net.rules' file.  Here we have
>>   additional challenges:
>>
>> ...
>>
>>   c) udev may not always be able to change a device's name.  If udev
>>      uses the kernel assignment namespace (ethN), then a rename of
>>      eth0->eth1 may require renaming eth1->eth0 (or something else).
>>      Udev operates on a single device instance at a time, it becomes
>>      difficult to switch names around for multiple devices, within
>>      the single namespace.
>
> I would classify this as a bug, especially the fact that udev doesn't
> undo a failed rename, so you end up with ethX_rename. Virtual devices
> using the same MAC address trigger this reliably unless you add
> exceptions to the udev rules.

This is handled in most cases. Virtual interfaces claiming a
configured name and created before the "hardware" interface are not
handled, that's right, but pretty uncommon.

> You state that it only operates on one device at a time. If that is
> correct, I'm not sure why the _rename suffix is used at all instead
> of simply trying to assign the final name, which would avoid this
> problem.

How? The kernel assignes the names and the configured names may
conflict. So you possibly can not rename a device to the target name
when it's name is already taken. I don't see how to avoid this.

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/