From: Matt Domsch <Matt_Domsch@dell.com>
To: linux-hotplug@vger.kernel.org
Subject: net device renaming 2-step, IFNAMSIZ limit
Date: Mon, 29 Nov 2010 03:29:09 +0000 [thread overview]
Message-ID: <20101129032908.GA29904@auslistsprd01.us.dell.com> (raw)
Once again, IFNAMSIZ bites me.
I see this in the udev debug logs when using biosdevname (which I
finally got working with SR-IOV devices tonight):
renamed network interface eth60 to eth60-pci2#0_60
renamed network interface eth60-pci2#0_60 to pci2#0_60
So, it worked, however, note that the rename happens in 2 steps, the
middle step of which uses a name that's dangerously close to
IFNAMSIZ, in fact it is 15 chars there.
In my testing, I'm doing:
modprobe ixgbe max_vfsc
which generates ethN..(N+127) interfaces (yes, 128 new interfaces) on
this dual-port card. Combine that with the longer names that
biosdevname is suggesting:
pciNN#PP_VVV
which is itself already 12 chars if all the fields are used to their
maximum length, and the concatenation of <oldname>-<newname> is way
past IFNAMSIZ.
I need a solution in which the intermediate name doesn't exceed 15
characters, and is guaranteed to be unique, as there may be lots of
udev instances running in parallel trying to do the same thing.
Ideas?
(note, vconfig can create VLANs for interfaces, which needs another 5
characters appended on the end, but that's for another day).
Thanks,
Matt
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
next reply other threads:[~2010-11-29 3:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 3:29 Matt Domsch [this message]
2010-12-07 2:45 ` net device renaming 2-step, IFNAMSIZ limit Piter PUNK
2010-12-07 3:54 ` Matt Domsch
2011-01-29 15:23 ` Matt Domsch
2011-02-08 14:42 ` Kay Sievers
2011-02-08 18:07 ` Scott James Remnant
2011-02-09 16:21 ` Matt Domsch
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=20101129032908.GA29904@auslistsprd01.us.dell.com \
--to=matt_domsch@dell.com \
--cc=linux-hotplug@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).