linux-kernel - Re: iwlagn: memory corruption with WPA enterprise

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]

Date:	Mon, 21 Nov 2011 14:09:16 +0100
From:	Tomáš Janoušek <tomi@...i.cz>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
Cc:	linux-kernel@...r.kernel.org, Wey-Yi Guy <wey-yi.w.guy@...el.com>,
	linux-wireless@...r.kernel.org
Subject: Re: iwlagn: memory corruption with WPA enterprise

Hello,

On Mon, Nov 21, 2011 at 02:05:28PM +0100, Stanislaw Gruszka wrote:
> The farther we get the problem is more and more strange.
> 
> Device that write to wrong address, would generate:
> 
> DMAR:[DMA Write] Request device [00:02.0] fault addr 6df084000
> DMAR:[fault reason 05] PTE Write access is not set

And that's exactly what happens if I don't disable firewire-ohci, because of
that stupid Ricoh multifunction blah blah issue.

> But only if
> 
> PCI-DMA: Using DMAR IOMMU
> 
> was printed in dmesg before. DMAR can be disabled by graphics
> driver, or maybe by other drivers too. Then above print will
> be missed in dmesg and protection would not work.
> 
> Try "dmesg | grep DMAR" to see if DMA remapping is really is
> in use. 

Well, this message is not printed, but as I said, loading firewire-ohci
triggers DMAR faults, so it should be in use anyway.

-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/
--
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/