netdev - Re: [Bugme-new] [Bug 14147] New: System unresponsive if I unplug network cable while ethtool -p is running

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

Message-Id: <20090911125546.52185035.akpm@linux-foundation.org>
Date:	Fri, 11 Sep 2009 12:55:46 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	netdev@...r.kernel.org
Cc:	bugzilla-daemon@...zilla.kernel.org,
	bugme-daemon@...zilla.kernel.org, david.graham@...el.com
Subject: Re: [Bugme-new] [Bug 14147] New: System unresponsive if I unplug
 network cable while ethtool -p is running


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Wed, 9 Sep 2009 00:06:10 GMT
bugzilla-daemon@...zilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=14147
> 
>            Summary: System unresponsive if I unplug network cable while
>                     ethtool -p is running
>            Product: Networking
>            Version: 2.5
>     Kernel Version: 2.6.30
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: acme@...stprotocols.net
>         ReportedBy: david.graham@...el.com
>         Regression: No
> 
> 
> When a user runs the "ethtool -p ethX" to identify the physical interface by
> flashing the appropriate interface LED, and then removes the cable at that
> interface, the keyboard locks up. This is naturally annoying to customers with
> multi-port systems, who wish to use ethtool -p so that they can
> disconnect/connect interface cables to appropriate ports. 
> 
> I am told that this is because "the RTNL lock is held by ethtool, and the link
> [down] message needs the RTNL", which would, I think, make this a kernel issue. 
> 
> This has been known about within INTEL for over 3 years, but only recently come
> to my attention. I have verified it on a 2.6.30 system using a default kernel
> configuration and the e1000e driver.
> 

hah.  cute.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html