linux-kernel - Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <20160824201444.487022de@free-electrons.com>
Date:   Wed, 24 Aug 2016 20:14:44 +0200
From:   Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To:     lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
Cc:     Ralph Sennhauser <ralph.sennhauser@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Gregory CLEMENT <gregory.clement@...e-electrons.com>
Subject: Re: [Regression?] Commit cb4f71c429 deliberately changes order of
 network interfaces

Hello,

On Wed, 24 Aug 2016 14:07:27 -0400, Lennart Sorensen wrote:

> > The nice thing about having the order in the dtb I thought was that it
> > wont ever change.  
> 
> I wonder, if someone was to build a box with this cpu, and add a PCIe
> network device, which order would they get probed in?  Any chance the
> PCIe could grab eth0 before the mvneta devices get probed?

Depends on the network driver I believe. But with an e1000e NIC plugged
in a PCIe slot, it indeed gets assigned as eth0, and the internal
mvneta devices get eth1, eth2, etc.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com