netdev - Re: tg3: regression of netdev stats

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: <87y5e6wcv1.fsf@devron.myhome.or.jp>
Date:	Sat, 02 Mar 2013 15:10:42 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	"Michael Chan" <mchan@...adcom.com>
Cc:	nsujir@...adcom.com, davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: tg3: regression of netdev stats

"Michael Chan" <mchan@...adcom.com> writes:

> On Fri, 2013-03-01 at 22:21 +0900, OGAWA Hirofumi wrote: 
>> Hi,
>> 
>> f4a46d1f46a8fece34edd2023e054072b02e110d (tg3: Prevent spurious tx
>> timeout by setting carrier off before tx disable.) seems to add the bug.
>> 
>> On 3.8.1 (I didn't use 3.7.x series), "ifconfig" commands doesn't show
>> any stats, i.e. all stats are zero.
>
> No stats on an active device transmitting and receiving packets?  I
> don't seem to see the same problem, but we'll look into this further.
> Thanks.

Yes, /proc/net/dev didn't show any packet traffic stats (always
zero). But, e.g. ping/nfs itself works fine.

BTW, chip is

02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57788 Gigabit Ethernet PCIe [14e4:1691] (rev 01)

tg3 0000:02:00.0 eth0: Tigon3 [partno(BCM57788) rev 57780001] (PCI Express) MAC address d4:be:d9:a6:a3:3b
tg3 0000:02:00.0 eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=200:01)

>> And bisect points the above commit.
>> In fact, reverting the above patch fixes the regression of netdev stats.
>> 
>> This patch looks like strange, and I'm not sure what this want to do.
>> Any ideas?
>
> Every time we reset the device (ethtool, MTU change, etc), we need to
> turn off all the tx queues before resetting.  As soon as we turn off
> these queues, if we don't turn off carrier, a tx timeout may be
> triggered if it's been more than 5 seconds since the last transmit on
> any of the tx queues.  These tx timeouts cause unnecessary concern to
> the user.

Hmm...  I'm not reading codes almost, so this might be wrong
though. tg3_phy_reset() set off if ->link_up, so this seems to be not
saving original state, and I'm not sure what want to do with ->link_up.

I felt the following pesudo code might be work and simple...

	ok = netif_carrier_ok()
        netif_carrier_off()

	[reconfigure...]

        if (ok)
        	netif_carrier_on()

Thanks.
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
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