lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 10 Jul 2014 12:46:58 +0200
From:	Tom Gundersen <>
To:	Ian Campbell <>
Cc:	netdev <>,
	LKML <>,
	David Miller <>,
	David Herrmann <>,
	Kay Sievers <>, Wei Liu <>,
	xen-devel <>
Subject: Re: [PATCH v7 15/33] net: xen-netback - set name assign type

On Thu, Jul 10, 2014 at 11:01 AM, Ian Campbell <> wrote:
> On Thu, 2014-07-10 at 10:17 +0200, Tom Gundersen wrote:
>> The name contains then xen handle, which is not guaranteed to be
>> stable between restarts, so label this NET_NAME_ENUM.
> FWIW the N'th interface for domain with domid D will always be named
> vifD.N.
> If you reboot domain D then it's domid will change to E and the new
> device will be vifE.N.
> I don't know if that counts as predictable as far as the interface you
> are introducing is concerned.

That was my understanding, thanks for confirming.

The idea is that the same interface on the same machine must get the
same name between reboots in order to be considered predictable. So
under the assumption that a rebooted domain should be considered "the
same machine" (i.e., it still has the same local configuration,
possibly referencing the interface names), then we should consider the
names not predictable, so NET_NAME_ENUM.


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

Powered by blists - more mailing lists