| 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
| ||
|
Message-ID: <20111031160342.GB2225@redhat.com> Date: Mon, 31 Oct 2011 17:03:43 +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 On Sat, Oct 29, 2011 at 07:15:54PM +0200, Tomáš Janoušek wrote: > Is there anything I can do to track this down? Perhaps try some experimental > uCode or something? 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. You have to compile kernel with CONFIG_DEBUG_PAGEALLOC and add corrupt_dbg=1 to catch memory corruption. However that may not work if you have small amount of memory. Also would be good to enable other debug options: CONFIG_DEBUG_OBJECTS=y CONFIG_DEBUG_OBJECTS_FREE=y CONFIG_DEBUG_OBJECTS_TIMERS=y CONFIG_DEBUG_OBJECTS_WORK=y CONFIG_DEBUG_OBJECTS_RCU_HEAD=y CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1 CONFIG_DEBUG_SG=y CONFIG_DEBUG_LIST=y 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/
Powered by blists - more mailing lists