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: <ed0d524976663f40412b1852e16099f8@agner.ch>
Date:	Tue, 12 Apr 2016 00:25:02 -0700
From:	Stefan Agner <stefan@...er.ch>
To:	David Miller <davem@...emloft.net>
Cc:	systemd-devel@...ts.freedesktop.org, netdev@...r.kernel.org,
	fabio.estevam@...escale.com, l.stach@...gutronix.de,
	u.kleine-koenig@...gutronix.de, bryan.wu@...onical.com,
	bob.ham@...labora.com
Subject: Re: Configuring ethernet link fails with No such device

On 2016-04-11 18:29, David Miller wrote:
> From: Stefan Agner <stefan@...er.ch>
> Date: Mon, 11 Apr 2016 15:46:08 -0700
> 
>> What is the expectation/definition when link configuration should be
>> possible? Only after the network device got opened or before?
> 
> Only after it is open.  Drivers almost always have the entire chip in
> powerdown state when it is not open, so we wouldn't be able to
> properly do link settings even if we wanted to when the device is
> closed.

I see. Afact it is a udev rule which triggers the built-in link setup
code:
https://github.com/systemd/systemd/blob/09541e49ebd17b41482e447dd8194942f39788c0/rules/80-net-setup-link.rules

The udev rule is triggering on action add (=> probe on driver level). At
least on the device I tested, it seems that there is no event on open...
Any other ideas what could be used as trigger to configure the link?

--
Stefan