The patch titled jprobes: make struct jprobe.entry a void * has been added to the -mm tree. Its filename is jprobes-make-struct-jprobeentry-a-void.patch *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: jprobes: make struct jprobe.entry a void * From: Michael Ellerman <michael@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx> Cc: Prasanna S Panchamukhi <prasanna@xxxxxxxxxx> Cc: Ananth N Mavinakayanahalli <ananth@xxxxxxxxxx> Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@xxxxxxxxx> Cc: David S. Miller <davem@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- include/linux/kprobes.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN include/linux/kprobes.h~jprobes-make-struct-jprobeentry-a-void include/linux/kprobes.h --- a/include/linux/kprobes.h~jprobes-make-struct-jprobeentry-a-void +++ a/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); _ Patches currently in -mm which might be from michael@xxxxxxxxxxxxxx are jprobes-make-struct-jprobeentry-a-void.patch jprobes-remove-jprobe_entry.patch jprobes-make-jprobes-a-little-safer-for-users.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html