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: Wed, 20 Sep 2006 01:08:45 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Mathieu Desnoyers <compudj@...stal.dyndns.org> Cc: Martin Bligh <mbligh@...gle.com>, prasanna@...ibm.com, Andrew Morton <akpm@...l.org>, "Frank Ch. Eigler" <fche@...hat.com>, Ingo Molnar <mingo@...e.hu>, Paul Mundt <lethal@...ux-sh.org>, linux-kernel <linux-kernel@...r.kernel.org>, Jes Sorensen <jes@....com>, Tom Zanussi <zanussi@...ibm.com>, Richard J Moore <richardj_moore@...ibm.com>, Michel Dagenais <michel.dagenais@...ymtl.ca>, Christoph Hellwig <hch@...radead.org>, Greg Kroah-Hartman <gregkh@...e.de>, Thomas Gleixner <tglx@...utronix.de>, William Cohen <wcohen@...hat.com>, ltt-dev@...fik.org, systemtap@...rces.redhat.com Subject: Re: [PATCH] Linux Kernel Markers Ar Maw, 2006-09-19 am 13:54 -0400, ysgrifennodd Mathieu Desnoyers: > Very good idea.. However, overwriting the second instruction with a jump could > be dangerous on preemptible and SMP kernels, because we never know if a thread > has an IP in any of its contexts that would return exactly at the middle of the > jump. No: on x86 it is the *same* case for all of these even writing an int3. One byte or a megabyte, You MUST ensure that every CPU executes a serializing instruction before it hits code that was modified by another processor. Otherwise you get CPU errata and the CPU produces results which vendors like to describe as "undefined". Thus you have to serialize, and if you are serializing it really doesn't matter if you write a byte, a paragraph or a page. Alan - 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