netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Provide ability to change default netdev name?
Date: Fri, 16 Aug 2013 16:48:38 -0700	[thread overview]
Message-ID: <520EBA56.4050301@candelatech.com> (raw)
In-Reply-To: <1376696468.11042.74.camel@deadeye.wl.decadent.org.uk>

On 08/16/2013 04:41 PM, Ben Hutchings wrote:
> On Fri, 2013-08-16 at 15:14 -0700, Ben Greear wrote:
>> The latest udev in Fedora 19 (and perhaps elsewhere) will no longer
>> implement rules that rename an interface from ethX to ethY.  Nor
>> wlanX or other 'kernel namespaces'.  The Fedora udev developers do not seem
>> interested in changing this back to the old behaviour, evidently they
>> had a hard time implementing it properly.
>
> There is an inherent problem that a new device can appear at any time
> under the exact name udev is trying to rename to.  I expect it is
> possible to do this properly but may be quite difficult to eliminate the
> possibility of deadlock.
>
> Still, if udev actively refuses to use the 'kernel namespaces' (rather
> than just being configured not to), that would be a bug.

I agree, but the Fedora udev developers do not.  I'm not sure
if other distros will follow or not.

>> This effectively makes it impossible to have network device names of ethX
>> consistent across reboots in systems with multiple NICs and/or drivers.
>>
>> One way to work around this would be allow the kernel to use a different
>> default netdev name (for instance, keth%d).  I'm thinking this would be
>> configured as a kernel command line argument.  Then, a small change to udev/systemd to
>> make the 'kernel namespaces' configurable by letting it understand this new kernel
>> command line argument should resolve the problem.
>>
>> Does this sound like something that could be accepted upstream?
>
> This sounds completely ridiculous.

Yeah, seems lame to hack around funky user-space, but
if udev folks will truly not fix this, then life is
going to suck for users wanting to use 'ethX' naming
schemes for their network devices.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

      reply	other threads:[~2013-08-17  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 22:14 Provide ability to change default netdev name? Ben Greear
2013-08-16 23:41 ` Ben Hutchings
2013-08-16 23:48   ` Ben Greear [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=520EBA56.4050301@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=bhutchings@solarflare.com \
    --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;
as well as URLs for NNTP newsgroup(s).