netdev - Re: [PATCH] Better MWI workaround for 21143 rev 65 chip errata

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: <20080405181931.GA30312@colo.lackof.org>
Date:	Sat, 5 Apr 2008 12:19:31 -0600
From:	Grant Grundler <grundler@...isc-linux.org>
To:	Jeff Garzik <jgarzik@...ox.com>
Cc:	Grant Grundler <grundler@...isc-linux.org>,
	Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
	netdev@...r.kernel.org, kyle@...isc-linux.org,
	zero@...onel-panic.org
Subject: Re: [PATCH] Better MWI workaround for 21143 rev 65 chip errata

On Fri, Apr 04, 2008 at 06:07:20PM -0400, Jeff Garzik wrote:
> Grant Grundler wrote:
>> On Tue, Mar 25, 2008 at 12:39:09PM +0100, Thomas Bogendoerfer wrote:
>>> From: Peter Horton <zero@...onel-panic.org>
>>>
>>> This patch works around the MWI bug on the DC21143 rev 65 Tulip by
>>> ensuring that the receive buffers don't end on a cache line boundary
>>> (as documented in the errata).
>>>
>>> This patch is required for the MIPS based Cobalt Qube/RaQ as
>>> supporting the extra PCI commands seems to reduce the chance of a hard
>>> lockup between the Tulip and the PCI bridge.
>>>
>>> Signed-off-by: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
>> Acked-by: Grant Grundler <grundler@...isc-linux.org>
>> thanks!
>> I haven't tested this but it looks correct to me.
>
> Wanna give it a quick test then someone bounce me the patch?  :)  I don't 
> have the original.

Tested on j6000 (parisc) with 2.6.25-rc6 + gcc 4.2.
Seems to be working fine.
I'll bounce it next.

thanks,
grant
--
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