Re: [PATCH] kprobes/x86: Check for invalid ftrace location in __recover_probed_insn()

2015-02-03 Thread Masami Hiramatsu
(2015/02/04 1:21), Petr Mladek wrote: > __recover_probed_insn() should always be called from an address where > an instructions starts. The check for ftrace_location() might help to > discover a potential inconsistency. Something goes terribly wrong when > an address inside the ftrace location is c

[PATCH] kprobes/x86: Check for invalid ftrace location in __recover_probed_insn()

2015-02-03 Thread Petr Mladek
__recover_probed_insn() should always be called from an address where an instructions starts. The check for ftrace_location() might help to discover a potential inconsistency. Something goes terribly wrong when an address inside the ftrace location is checked. Let's BUG() in this case. Suggested-b