[lkml]   [2014]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v7 10/33] net: dummy - set name assign type
On Thu, Jul 10, 2014 at 1:44 PM, Bjørn Mork <> wrote:
> Tom Gundersen <> writes:
>> The result of
>> modprobe dummy numdummies=2
>> is to create dummy0 and dummy1, always with the same names.
>> The result of
>> ip link add type dummy
>> is to create dummyX, where X depends on what came before.
> Which is no different. That's exacly what happens when
> "modprobe dummy numdummies=2" creates the two first interfaces.
> ip link add link wwan0 name dummy0 type vlan id 2
> modprobe dummy numdummies=2
> ends up with dummy1 and dummy2 created by the dummy driver.
> You are trying to make up differences that just aren't there.

Ah, good point. You are right. So the dummy interfaces should be
labelled NET_NAME_ENUM.

I suppose the distinction should be that statically created devices
like these should be NET_NAME_PREDICTABLE only if they fail when the
name they want is already taken (rather than just picking the next

Thanks for looking into this!


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2014-07-10 15:42    [W:0.335 / U:1.752 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site