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:	Wed, 9 Nov 2011 16:54:11 +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 Stanislaw,

On Mon, Oct 31, 2011 at 05:03:43PM +0100, Stanislaw Gruszka wrote:
> You may try debugging patches I posted a while ago:
> http://marc.info/?l=linux-mm&m=131914560820378&w=2
> http://marc.info/?l=linux-mm&m=131914560820293&w=2
> http://marc.info/?l=linux-mm&m=131914560820317&w=2
> 
> With a bit of luck, kernel should panic and dump call-trace when
> bad code start to write at memory addresses where is not suppose
> to.

Thanks for your suggestions. I did as you told me, applied those 3 patches on
top of 3.1 + net-next (the one from 29 Oct 2011), enabled all those things in
config and passed corrupt_dbg=1 on cmdline, but the problem happens without
anything being written to dmesg.

Am I just lacking a bit of luck, or could it mean something (like that the
error is in hardware, the microcode, or something like that)?

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/