| 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: <1903109583.729928.1437397235777.JavaMail.zimbra@redhat.com> Date: Mon, 20 Jul 2015 09:00:35 -0400 (EDT) From: Kamil Paral <kparal@...hat.com> To: linux-kernel@...r.kernel.org Subject: bug: deadlock in smp.c at on_each_cpu/smp_call_function_many Hello, I've experienced a kernel panic, the screenshots are here: https://bugs.freedesktop.org/attachment.cgi?id=117026 https://bugs.freedesktop.org/attachment.cgi?id=117027 It happened with kernel-4.0.7-300.fc22.x86_64 on Fedora 22. Originally I reported it against the radeon driver [1], but I was told that it seems to be a deadlock in on_each_cpu/smp_call_function_many (which seems to be in smp.c) and that I should report it into an appropriate mailing list. I'd report it to bugzilla, but I wasn't sure which product/component to file it against. Please advise what steps I should take in order to have this properly reported, or whether random panics which are not reproducible at will are not worth reporting, because the traces don't provide enough clues to resolve them. I have no experience in this matter, so I don't really know. Thanks for pointers, Kamil Paral [1] https://bugs.freedesktop.org/show_bug.cgi?id=91291 -- 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