Re: [PATCH -tip V3] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Hi Masami, [auto build test WARNING on tip/auto-latest] [also build test WARNING on v4.13-rc2 next-20170727] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH -tip V3] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Hi Masami, [auto build test WARNING on tip/auto-latest] [also build test WARNING on v4.13-rc2 next-20170727] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH -tip V3] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

On Tue, 25 Jul 2017 23:54:49 +0900 Masami Hiramatsu wrote: > Since the kernel segment registers are not prepared at the > entry of irq-entry code, if a kprobe on such code is > jump-optimized, accessing per-cpu variables may cause > kernel panic. > However, if the kprobe is

Re: [PATCH -tip V3] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

On Tue, 25 Jul 2017 23:54:49 +0900 Masami Hiramatsu wrote: > Since the kernel segment registers are not prepared at the > entry of irq-entry code, if a kprobe on such code is > jump-optimized, accessing per-cpu variables may cause > kernel panic. > However, if the kprobe is not optimized, it

[PATCH -tip V3] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Since the kernel segment registers are not prepared at the entry of irq-entry code, if a kprobe on such code is jump-optimized, accessing per-cpu variables may cause kernel panic. However, if the kprobe is not optimized, it kicks int3 exception and set segment registers correctly. This checks

[PATCH -tip V3] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Since the kernel segment registers are not prepared at the entry of irq-entry code, if a kprobe on such code is jump-optimized, accessing per-cpu variables may cause kernel panic. However, if the kprobe is not optimized, it kicks int3 exception and set segment registers correctly. This checks