netdev - Re: followup: what's responsible for setting netdev->operstate to IF_OPER

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 26 Aug 2018 21:24:45 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     "Robert P. J. Day" <rpjday@...shcourse.ca>
Cc:     Linux kernel netdev mailing list <netdev@...r.kernel.org>
Subject: Re: followup: what's responsible for setting netdev->operstate to
 IF_OPER_DOWN?

On Sun, Aug 26, 2018 at 11:14:33AM -0400, Robert P. J. Day wrote:
> 
>   apologies for the constant pleas for assistance, but i think i'm
> zeroing in on the problem that started all this. recap: custom
> FPGA-based linux box with multiple ports, where the current symptom is
> that there is no userspace notification when someone simply unplugs
> one of the ports ("ifconfig" shows that interface still RUNNING).

What are you using for a PHY? Are you using phylib or phylink?  I
strongly suggest you do, and then you don't need to care about any of
this.

	Andrew