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, 6 Mar 2014 16:17:47 -0300
From:	Ezequiel Garcia <>
To:	Andrew Lunn <>
Cc:	Thomas Petazzoni <>,, Jason Cooper <>,
	Tawfik Bayouk <>,, Nadav Haklai <>,
	Lior Amsalem <>,
	Gregory CLEMENT <>,,
	Sebastian Hesselbarth <>
Subject: Re: [PATCH] ARM: mvebu: add Device Tree for the Armada 385 RD board

On Mar 06, Andrew Lunn wrote:
> > Can't we fix this so the probe order doesn't affect the name?
> > 
> > Is that sane?
> You are not supposed to trust the device name, since probing can
> happen in parallel, on different buses. udev should have rules to name
> the interfaces based on the MAC address. On my Debian system i have:
> /etc/udev/rules.d/70-persistent-net.rules
> So what is important is that the MAC addresses are assigned correctly
> to the device. And DT does that based on MMIO address, so should be
> reliable, independent of probe order.

Right, makes perfect sense!

So we can just keep the nodes address-ordered, without caring about the name?

Ezequiel GarcĂ­a, Free Electrons
Embedded Linux, Kernel and Android Engineering
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