| 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: Mon, 07 Aug 2006 09:18:22 +0100 From: "Jan Beulich" <jbeulich@...ell.com> To: "Andi Kleen" <ak@....de>, "Andrew Morton" <akpm@...l.org> Cc: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com>, <torvalds@...l.org>, <davej@...hat.com>, <linux-kernel@...r.kernel.org> Subject: Re: 2.6.18-rc3-g3b445eea BUG: warning at /usr/src/linux-git/kernel/cpu.c:51/unlock_cpu_hotplug() >> It's a false-positive in this case - the backtrace was complete. It would >> be good if we could make the did-we-get-stuck detector a bit smarter. Even >> special-casing "sysenter_past_esp" would stop a lot of this.. > >Actually it's not completely false in this case -- it should >have reached user mode and stopped there, but for some reason >I didn't and already stopped still in the kernel. > >Most likely the CFI annotation for that sysenter path is not complete. Correct, the return point of sysexit (SYSENTER_RETURN) is still in kernel space, but its annotations are invisible to the unwinder. We should make the VDSO be treated as user-mode code despite living above PAGE_OFFSET. >It's on my todo list to investigate but I still hope Jan does it first ;-) I'll try to, once I've got through moving the Xen code from 2.6.16 to 2.6.18-rc3 Jan - 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