On Tue, 25 Nov 2014, Steven Rostedt wrote: > It is not guaranteed from ftrace's stand point. What happens if we have > a kprobe handler that modifies it for someplace else? Changing the ip > address may not be a kpatch/kGraft privilege only.
This brings me back to the RFC patch I sent back then in october ... what we really want to do is to at least warn about situations when we are going to redirect code flow (through IPMODIFY) for function that has a kprobe installed anywhere inside it. Otherwise the probe will silently vanish (there is no way how to migrate it to the new function automatically), which might be very confusing for uses (cosider systemtap, for example). I'll resurect my patch if noone beats me doing it. It should go in together with the live patching framework I believe. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
