netdev - Re: PROBLEM: tg3 spitting out uninitialized memory

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] [day] [month] [year] [list]

Message-ID: <1551EAE59135BE47B544934E30FC4FC09400A1@nt-irva-0751.brcm.ad.broadcom.com>
Date:	Sun, 15 Apr 2007 23:43:03 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Andi Kleen" <andi@...stfloor.org>
cc:	"Jamie webb" <j@...bb.sygneca.com>, netdev@...r.kernel.org
Subject: Re: PROBLEM: tg3 spitting out uninitialized memory

Andi Kleen wrote:

> tg3s never use the IOMMU on AMD systems with production kernels
> because they have a suitably large DMA mask. IOMMU is only used
> there to remap memory that doesn't fit a device's DMA mask.
> There is a debugging mode to force iommu always, but it is not used 
> unless you configure it specially.

We actually have one chip that uses a 32-bit mask, and some that use
a 40-bit mask.  But you're right, I don't know for a fact whether it
was IOMMU or not.  The corruption happened on 64-bit chunks and seemed
to have gone away after upgrading to the latest kernel, according to
the user.


-
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