netdev - rx-over-length stats problem with e100

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: <4F3C5491.7090600@candelatech.com>
Date:	Wed, 15 Feb 2012 16:57:53 -0800
From:	Ben Greear <greearb@...delatech.com>
To:	netdev <netdev@...r.kernel.org>,
	e1000-devel list <e1000-devel@...ts.sourceforge.net>
Subject: rx-over-length stats problem with e100

While testing my rx-all patches, I triggered a code branch
that caused the rx_over_length_errors counter to increment
in the e100_rx_indicate path (it can already increment there
w/out my patch, it appears).

The problem is that then the stats go weird because the code in
e100_update_stats adds the total rx_over_length_errors each time
it's called, and does not reset the rx_over_length_errors to zero:

		ns->rx_length_errors += le32_to_cpu(s->rx_short_frame_errors) +
			nic->rx_over_length_errors;


So, should we zero out that counter after reading it (although that
might race)?  Any idea how this is supposed to work?

Thanks,
Ben

-- 
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com

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