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:	Mon, 21 Nov 2011 15:32:26 +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:40:57PM +0100, Stanislaw Gruszka wrote:
> On Mon, Nov 21, 2011 at 02:09:16PM +0100, Tomáš Janoušek wrote:
> > And that's exactly what happens if I don't disable firewire-ohci, because of
> > that stupid Ricoh multifunction blah blah issue.
> 
> So maybe problem is caused by Ricoh, not by iwlagn. But if so 
> why blacklisting iwlagn help? Wired. Did you disable firewire in
> BIOS, or just blacklist module?

I don't think so. The problem with Ricoh is that it has two PCI devices:
0d:00.0 and 0d:00.3, but both use 0d:00.0 in DMA requests, which triggers DMAR
faults.  Of course, I can try disabling that in BIOS, but I doubt it will
change anything.

> Ok maybe let's try to find some better reproducer first.
> I wrote simple program that fill memory with some pattern, and
> then check every one second if pattern is still there.
> It can be used like:
> ./checkmem 100M 30M
> where first argument is size of memory it will alloc and check,
> second specify number of internal loops to make cpu busy (bigger
> value will cause more cpu power consumption). Many instances of
> the program can be running at once.
> 
> Tomáš, please try to reproduce with that program, I'm attaching
> it. When corruption will be detected, checkmem will print invalid
> values, maybe would be possible to find out what contents is
> written to memory.

Okay, I'll try that later. Yesterday I tried to use memtester [1] to catch the
problem, but it never occured in it. Kernel compilation was segfaulting and
that tool was running alongside being all happy. But maybe it has different
memory usage pattern or something. Anyway, I'll try your program and if it
doesn't work, I'll make it so. :-)

[1] http://pyropus.ca/software/memtester/

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/