Re: [PATCH -tip v2] kprobes: Prohibit probing on BUG() and WARN() address

2019-09-04 Thread Steven Rostedt
On Tue, 3 Sep 2019 20:08:21 +0900 Masami Hiramatsu wrote: > Since BUG() and WARN() may use a trap (e.g. UD2 on x86) to > get the address where the BUG() has occurred, kprobes can not > do single-step out-of-line that instruction. So prohibit > probing on such address. > > Without this fix, if s

Re: [PATCH -tip v2] kprobes: Prohibit probing on BUG() and WARN() address

2019-09-04 Thread Naveen N. Rao
Masami Hiramatsu wrote: Since BUG() and WARN() may use a trap (e.g. UD2 on x86) to get the address where the BUG() has occurred, kprobes can not do single-step out-of-line that instruction. So prohibit probing on such address. Without this fix, if someone put a kprobe on WARN(), the kernel will

[PATCH -tip v2] kprobes: Prohibit probing on BUG() and WARN() address

2019-09-03 Thread Masami Hiramatsu
Since BUG() and WARN() may use a trap (e.g. UD2 on x86) to get the address where the BUG() has occurred, kprobes can not do single-step out-of-line that instruction. So prohibit probing on such address. Without this fix, if someone put a kprobe on WARN(), the kernel will crash with invalid opcode