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]

Message-ID: <20111114140714.GD2513@redhat.com>
Date:	Mon, 14 Nov 2011 15:07:15 +0100
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Tomáš Janoušek <tomi@...i.cz>
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

Hi,

On Fri, Nov 11, 2011 at 04:01:05PM +0100, Tomáš Janoušek wrote:
> Could you please elaborate on that thing with enabling IOMMU? The only thing I
> know about IOMMU is that it is somehow related to VT-d (passing whole PCI
> devices to virtual guests), and that I have to pass intel_iommu=off to kernel
> command line, otherwise the machine doesn't even boot. Is that a problem?
Yes. That mean iommu software or hardware is broken on your system.

I have no other ideas how to track this down. I think now, this is
a firwmare issue. BTW, you suspected that from very beginning :-)
This could be also a driver issue, but AFAICT programing DMA do not
differ on 6205 from other devices, so bug in firmware is much more
probable reason of corruption.

Stanislaw
--
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/