linux-kernel - Re: bad DMAR interaction with iwlagn and SATA

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: <1222441955.3798.13.camel@johannes.berg>
Date:	Fri, 26 Sep 2008 17:12:35 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Muli Ben-Yehuda <muli@...ibm.com>
Cc:	Jeff Garzik <jeff@...zik.org>, Andres Freund <andres@...razel.de>,
	linux-kernel@...r.kernel.org,
	linux-wireless <linux-wireless@...r.kernel.org>,
	Tomas Winkler <tomasw@...il.com>
Subject: Re: bad DMAR interaction with iwlagn and SATA

On Fri, 2008-09-26 at 17:47 +0300, Muli Ben-Yehuda wrote:

> The way to debug this is to figure out why device 00:1f.2 is trying to
> read from DMA address fffbf000 and does not have permission to do
> so. This could be indicative of a driver bug where it is programming
> the device to read from some buffer that has not been allocated
> through the DMA API and thus does not have a valid IOMMU mapping, or a
> hardware quirk where the device tries to read from memory without host
> involvement. The former is much more likely.

The same is probably true for the iwlagn case which was

> [ 4184.617392] DMAR:[DMA Read] Request device [03:00.0] fault addr fa946000 
> [ 4184.617393] DMAR:[fault reason 06] PTE Read access is not set
> [ 4184.644081] iwlagn: Microcode HW error detected.  Restarting.

and indeed matches experience from myself and Marcel that DMA bugs seem
to lurk.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)