netdev - Re: [PATCH] tg3: ethtool phys

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: <1203831726.8232.115.camel@lb-tlvb-eliezer.il.broadcom.com>
Date:	Sun, 24 Feb 2008 07:42:06 +0200
From:	"Eliezer Tamir" <eliezert@...adcom.com>
To:	"David Miller" <davem@...emloft.net>
cc:	mchan@...adcom.com, shemminger@...tta.com, jgarzik@...ox.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH] tg3: ethtool phys_id default (rev2)


On Sat, 2008-02-23 at 19:52 -0800, David Miller wrote:
> From: "Michael Chan" <mchan@...adcom.com>
> Date: Fri, 22 Feb 2008 11:16:42 -0800
> 
> > On Fri, 2008-02-22 at 10:24 -0800, Stephen Hemminger wrote:
> > > When asked to blink LEDs the tg3 driver behaves when using:
> > > 	ethtool -p ethX
> > > The default value for data is zero, and other drivers interpret this
> > > as blink forever (or at least a really long time).  The tg3 driver
> > > interprets this as blink once.  All drivers should have the same
> > > behaviour.
...
> > We should do this across the board for bnx2, bnx2x, and niu as well.
> 
> Agreed.

Doesn't this mean that ethtool -p will hold the RTNL lock forever?
Is this a good idea?

For example on the Red Hat machine I have here if you do:

ethtool -p eth2 100000 &
reboot

Various things the shutdown scripts try to do will fail because of the
held RTNL lock. in the end the script dies and the machine does not
reboot.

Eliezer





--
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