netdev - how PHY driver is notified that cable is unplugged? (possibly related to IFF

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-next>] [day] [month] [year] [list]

Message-ID: <20180801085826.Horde.rj4qsfJlofF1IKzzUQgwFrO@crashcourse.ca>
Date:   Wed, 01 Aug 2018 08:58:26 -0400
From:   rpjday@...shcourse.ca
To:     netdev@...r.kernel.org
Subject: how PHY driver is notified that cable is unplugged? (possibly
 related to IFF_RUNNING flag)

   (warning that i have a few questions that are probably trivial  
until i get up to speed
with networking code.)

   a colleague asked for advice about the following -- apparently a  
new PHY driver works
properly when being brought up with "ifconfig <ifname> up", part of  
that process
apparently setting the IFF_RUNNING net_device flags bit. so far, so good.

   now, when the cable is physically unplugged, the claim is that  
there is no obvious
status change for that port, accompanied by the suggestion that it is  
that IFF_RUNNING
flag bit that is not being unset.

   asking a more general question, where can i read up on the proper  
protocol for
a driver being notified of, and properly handling, physical  
disconnection on that
port? and, of course, the cable being plugged back in.

   thanks in advance for any pointers.

rday