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: <20081031093924.GG30317@elte.hu> Date: Fri, 31 Oct 2008 10:39:24 +0100 From: Ingo Molnar <mingo@...e.hu> To: Jeremy Fitzhardinge <jeremy@...p.org> Cc: Suresh Siddha <suresh.b.siddha@...el.com>, "jens.axboe@...cle.com" <jens.axboe@...cle.com>, "paulmck@...ux.vnet.ibm.com" <paulmck@...ux.vnet.ibm.com>, "nickpiggin@...oo.com.au" <nickpiggin@...oo.com.au>, "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Mallick, Asit K" <asit.k.mallick@...el.com> Subject: Re: [patch] generic-ipi: fix the smp_mb() placement * Jeremy Fitzhardinge <jeremy@...p.org> wrote: > Suresh Siddha wrote: >> We didn't see the lockup in our tests but Xen folks reported similar failures >> with their smp call function code. >> > > ...really? I don't remember anything like that, but perhaps I'm > forgetting something. In Xen the IPI is sent with a hypercall, > which is definitely a solid enough barrier for these purposes. i think Suresh might be referring to some of the fragilities Xen had with generic-ipi. But those AFAICT were due to the on-stack lifetime bug that Nick fixed via the kmalloc? v2.6.26-ish issue. Ingo -- 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