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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 11 Nov 2011 16:01:05 +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 Fri, Nov 11, 2011 at 06:47:31AM +0100, Stanislaw Gruszka wrote:
> On Thu, Nov 10, 2011 at 05:30:51PM +0100, Tomáš Janoušek wrote:
> > I think all those T520 and T420s models have exactly the same wireless card. I
> > don't see why they wouldn't have. :-)
>
> Well, laptops models have common mainboards, but peripheral components
> might not be identical. Especially wireless card might vary from unit
> to unit. For example:
> 
> T520 with iwl6300:
> http://smolt.fedoraproject.org/client/show/pub_0cbc8731-47d3-4ecf-8add-aa832b34edcd
> T520 with iwl1000:
> http://smolt.fedoraproject.org/client/show/pub_02f601d6-7a93-4c0e-bc01-a4a95db36086 
> T520 with iwl6205:
> http://smolt.fedoraproject.org/client/show/pub_0232252f-75a9-4050-a69b-c8e95e00eaf2

These links don't work, but my colleagues indeed do have iwl6205. They are,
however, running 64-bit kernels, so I tried doing the same and I haven't been
able to reproduce the issue for the past few hours. So it seems like it
happens on 32-bit kernels only. This looks like a good workaround (better than
getting a different wireless card), so I can run 64-bit during working days
and experiment with 32-bit when I have time to debug this.

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?

Kind regards,
-- 
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/