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: Tue, 26 Jun 2007 11:48:50 +1000 (EST) From: Michael Ellerman <michael@...erman.id.au> To: <linux-kernel@...r.kernel.org> Cc: <linuxppc-dev@...abs.org>, <linux-ia64@...r.kernel.org>, <linux-arch@...r.kernel.org>, Andrew Morton <akpm@...l.org>, Christoph Hellwig <hch@....de>, <anil.s.keshavamurthy@...el.com>, <ananth@...ibm.com> Subject: [PATCH 1/3] Make struct jprobe.entry a void * Currently jprobe.entry is a kprobe_opcode_t *, but that's a lie. On some platforms it doesn't point to an opcode at all, it points to a function descriptor. It's really a pointer to something that the arch code can turn into a function entry point. And that's what actually happens, none of the generic code ever looks at jprobe.entry, it's only ever dereferenced by arch code. So just make it a void *. Signed-off-by: Michael Ellerman <michael@...erman.id.au> --- It isn't obvious where kprobes patches should go, is anyone "the" maintainer? Instead I've just sent this to everyone who'd touched the code lately, or might be otherwise interested. include/linux/kprobes.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/linux/kprobes.h b/include/linux/kprobes.h index 23adf60..f4e53b7 100644 --- a/include/linux/kprobes.h +++ b/include/linux/kprobes.h @@ -116,7 +116,7 @@ struct kprobe { */ struct jprobe { struct kprobe kp; - kprobe_opcode_t *entry; /* probe handling code to jump to */ + void *entry; /* probe handling code to jump to */ }; DECLARE_PER_CPU(struct kprobe *, current_kprobe); -- 1.5.1.3.g7a33b - 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