Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-05-11 Thread Ingo Molnar
* Eugene Shatokhin wrote: > Hi, > > Now that the patch is in mainline (commit > c80e5c0c23ce2282476fdc64c4b5e3d3a40723fd) and kernel 4.1-rc1 is out, do you > mind if I send the backports of that patch to -stable? No objections from me! Thanks, Ingo -- To unsubscribe from this list:

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-05-11 Thread Ingo Molnar
* Eugene Shatokhin eugene.shatok...@rosalab.ru wrote: Hi, Now that the patch is in mainline (commit c80e5c0c23ce2282476fdc64c4b5e3d3a40723fd) and kernel 4.1-rc1 is out, do you mind if I send the backports of that patch to -stable? No objections from me! Thanks, Ingo -- To

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-04-27 Thread Eugene Shatokhin
Hi, Now that the patch is in mainline (commit c80e5c0c23ce2282476fdc64c4b5e3d3a40723fd) and kernel 4.1-rc1 is out, do you mind if I send the backports of that patch to -stable? Regards, Eugene -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-04-27 Thread Eugene Shatokhin
Hi, Now that the patch is in mainline (commit c80e5c0c23ce2282476fdc64c4b5e3d3a40723fd) and kernel 4.1-rc1 is out, do you mind if I send the backports of that patch to -stable? Regards, Eugene -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-03-17 Thread Masami Hiramatsu
(2015/03/17 0:03), Ingo Molnar wrote: > > * Masami Hiramatsu wrote: > >> (2015/03/09 20:19), Eugene Shatokhin wrote: >>> On x86-64, __copy_instruction() always returns 0 (error) if the >>> instruction uses %rip-relative addressing. This is because >>> kernel_insn_init() is called the second

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-03-17 Thread Masami Hiramatsu
(2015/03/17 0:03), Ingo Molnar wrote: * Masami Hiramatsu masami.hiramatsu...@hitachi.com wrote: (2015/03/09 20:19), Eugene Shatokhin wrote: On x86-64, __copy_instruction() always returns 0 (error) if the instruction uses %rip-relative addressing. This is because kernel_insn_init() is

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-03-16 Thread Ingo Molnar
* Masami Hiramatsu wrote: > (2015/03/09 20:19), Eugene Shatokhin wrote: > > On x86-64, __copy_instruction() always returns 0 (error) if the > > instruction uses %rip-relative addressing. This is because > > kernel_insn_init() is called the second time for 'insn' instance > > in such cases and

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-03-16 Thread Ingo Molnar
* Masami Hiramatsu masami.hiramatsu...@hitachi.com wrote: (2015/03/09 20:19), Eugene Shatokhin wrote: On x86-64, __copy_instruction() always returns 0 (error) if the instruction uses %rip-relative addressing. This is because kernel_insn_init() is called the second time for 'insn' instance

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-03-09 Thread Masami Hiramatsu
(2015/03/09 20:19), Eugene Shatokhin wrote: > On x86-64, __copy_instruction() always returns 0 (error) if the > instruction uses %rip-relative addressing. This is because > kernel_insn_init() is called the second time for 'insn' instance > in such cases and sets all its fields to 0. > > Because

[PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-03-09 Thread Eugene Shatokhin
On x86-64, __copy_instruction() always returns 0 (error) if the instruction uses %rip-relative addressing. This is because kernel_insn_init() is called the second time for 'insn' instance in such cases and sets all its fields to 0. Because of this, trying to place a Kprobe on such instruction

[PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-03-09 Thread Eugene Shatokhin
On x86-64, __copy_instruction() always returns 0 (error) if the instruction uses %rip-relative addressing. This is because kernel_insn_init() is called the second time for 'insn' instance in such cases and sets all its fields to 0. Because of this, trying to place a Kprobe on such instruction

Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()

2015-03-09 Thread Masami Hiramatsu
(2015/03/09 20:19), Eugene Shatokhin wrote: On x86-64, __copy_instruction() always returns 0 (error) if the instruction uses %rip-relative addressing. This is because kernel_insn_init() is called the second time for 'insn' instance in such cases and sets all its fields to 0. Because of