netdev - Re: b44: Reset due to FIFO overflow.

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: <20100630.132220.129754921.davem@davemloft.net>
Date:	Wed, 30 Jun 2010 13:22:20 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	james.dutton@...il.com
Cc:	eric.dumazet@...il.com, erblichs@...thlink.net,
	netdev@...r.kernel.org
Subject: Re: b44: Reset due to FIFO overflow.

From: James Courtier-Dutton <james.dutton@...il.com>
Date: Mon, 28 Jun 2010 11:17:59 +0100

> Interesting, which hardware, apart from the b44, is it that "requires"
> a hardware reset after a RX FIFO overflow.

This problem is quite common, actually.

Even though it shouldn't be, this is seemingly one of the least tested
paths of a networking chip.

You'd think the recovery would be easy, flush the fifos and drop the
packet, then rewind the RX descriptor pointer.

But it's not and I've seen everything from RX descriptor corruption
to random DMA splats elsewhere corrupting memory entirely, as a result
of a networking card taking a RX fifo overflow.
--
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