netdev - Re: Configuring ethernet link fails with No such device

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: <1460451492.6333.6.camel@collabora.com>
Date:	Tue, 12 Apr 2016 09:58:12 +0100
From:	Bob Ham <bob.ham@...labora.com>
To:	Stefan Agner <stefan@...er.ch>,
	systemd-devel@...ts.freedesktop.org, netdev@...r.kernel.org,
	davem@...emloft.net
Cc:	fabio.estevam@...escale.com, l.stach@...gutronix.de,
	u.kleine-koenig@...gutronix.de, bryan.wu@...onical.com
Subject: Re: Configuring ethernet link fails with No such device

On Mon, 2016-04-11 at 15:46 -0700, Stefan Agner wrote:

> The FEC driver (fec_main.c) does not initialize phy_dev until the
> device
> has been opened, and therefor the callback
> fec_enet_(get|set)_settings
> returns -19.

I saw the same problem with the FEC driver.  From what I recall, it
became clear that there was a problem with the driver returning from
the eth device initialisation before the PHY was initialised, which
apparently is Bad and Wrong.

> Or in other words: Is this a Kernel or systemd issue?

>From what I recall, both; an issue with the FEC driver, and issues in
systemd/udevd's handling of link-level settings.

-- 
Bob Ham <bob.ham@...labora.com>
Software Engineer

>>>>>>>>
Open First 
Collabora is hiring!
Please check out our latest opportunities here:
http://bit.ly/Collabora-Careers
<<<<<<<<