| 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
| ||
|
Date: Sun, 11 Apr 2010 09:47:05 -0700 (PDT) From: Ben Gamari <bgamari.foss@...il.com> To: Johannes Berg <johannes@...solutions.net> Cc: linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, ath9k@...ts.ath9k.org Subject: Re: [REGRESSION] Lockup inside of stop_machine() during modprobe aes (was Re: Another AR5008 hang) On Tue, 06 Apr 2010 11:08:22 -0700 (PDT), Ben Gamari <bgamari.foss@...il.com> wrote: > Hey all, > > I just built 2.6.34-rc3 with the appropriate fixes for the ACPI thermal lockdep > issues and have attached the dmesg output of the crash below. It appears that > modprobe is freezing with a few locks held while inserting aes.ko. In > particular, it seems that the kernel is deadlocking inside of stop_machine() > while flushing workqueues. > I can confirm that modprobing aes explicitly also results in the stop_machine() deadlock, so this doesn't appear to be an interaction with ath9k or the mac80211 subsystem. Furthermore, if I disable CONFIG_CRYPTO_AES_X86_64 (I'm on a Core Duo platform), aes loads as expected and things work as they should. Any ideas? I'm rather disturbed that this regression has still not had a single reply while -rc4 is so near. - Ben -- 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