linux-kernel - Re: Integrated MegaRAID controller and AMD IOMMU issue

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: <20130625093542.GR11309@8bytes.org>
Date:	Tue, 25 Jun 2013 11:35:42 +0200
From:	Joerg Roedel <joro@...tes.org>
To:	James Georgas <james.georgas@...oo.ca>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Integrated MegaRAID controller and AMD IOMMU issue

Hi James,

On Tue, Jun 25, 2013 at 12:12:53AM -0600, James Georgas wrote:
> I discussed the issue with an LSI engineer, and he said that since the
> integrated controller uses system memory, which it gets from the BIOS
> during initialization, there will be issues with the IOMMU. I assume
> he is referring to DMA address problems due to IOMMU translation.

Looks like the problem is in the LSI driver. The driver needs to dma-map
the system memory it gets from the BIOS (for example with dma_map_single)
and use the dma_handle returned for transactions. Otherwise the IOMMU
will block the accesses from the device and make it unusable.


	Joerg


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/