| 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: <CAMiJ5CU0K4b9xK+u1DRFsJBUE8Bp6NvZrUwZWHiiMRGA8Uqaig@mail.gmail.com> Date: Mon, 23 Feb 2015 11:01:09 -0300 From: Rafael David Tinoco <inaddy@...ntu.com> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Peter Zijlstra <peterz@...radead.org>, LKML <linux-kernel@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, Jens Axboe <axboe@...nel.dk>, Frederic Weisbecker <fweisbec@...il.com>, Gema Gomez <gema.gomez-solano@...onical.com>, chris.j.arges@...onical.com Subject: Re: smp_call_function_single lockups On Thu, Feb 19, 2015 at 2:14 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > > Hmm. Still just the stack trace for the CPU that is blocked (CPU0), if > you can get the core-file to work and figure out where the other CPU > is, that would be good. > This is v3.19 + your patch (smp acquire/release) - (nested kvm with 2 vcpus on top of proliant with x2apic cluster mode and acpi_idle) * http://people.canonical.com/~inaddy/lp1413540/STACK_TRACE.txt http://people.canonical.com/~inaddy/lp1413540/BACKTRACES.txt http://people.canonical.com/~inaddy/lp1413540/FOREACH_BT.txt * It looks like we got locked because of reentrant flush_tlb_* through smp_call_* but I'll leave it to you. let me know if you need any more info.. - Rafael Tinoco -- 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