On Wed, 14 Jan 2015 17:55:37 +0100 Borislav Petkov <bp@xxxxxxxxx> wrote: > Err, stupid question: marking the jprobe handler "notrace" doesn't help? > A few reasons. One, that would require all users to make their handler as "notrace". That's not very reliable. Not to mention, I still work at Red Hat and we have this KABI thingy, where the jprobe modules don't need to change and we still need to fix it. This change is much more robust that expecting jprobe callers to add notrace. Two, I HATE when a notrace is added for function graph tracing that is not needed for function tracing. As I told Masami, every "notrace" added to the kernel makes function tracing that much more useless. Function tracing should be allowed to debug jprobes. Three, I have a patch that lets this all work if the kprobe/jprobes uses the ftrace fentry infrastructure (the work I original did). Why break everything for something the requires jprobe users to do things correctly? -- Steve -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html