1. 24 4月, 2014 2 次提交
    • M
      kprobes, x86: Use NOKPROBE_SYMBOL() instead of __kprobes annotation · 9326638c
      Masami Hiramatsu 提交于
      Use NOKPROBE_SYMBOL macro for protecting functions
      from kprobes instead of __kprobes annotation under
      arch/x86.
      
      This applies nokprobe_inline annotation for some cases,
      because NOKPROBE_SYMBOL() will inhibit inlining by
      referring the symbol address.
      
      This just folds a bunch of previous NOKPROBE_SYMBOL()
      cleanup patches for x86 to one patch.
      Signed-off-by: NMasami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
      Link: http://lkml.kernel.org/r/20140417081814.26341.51656.stgit@ltc230.yrl.intra.hitachi.co.jp
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
      Cc: Borislav Petkov <bp@suse.de>
      Cc: Dave Hansen <dave.hansen@linux.intel.com>
      Cc: Fernando Luis Vázquez Cao <fernando_b1@lab.ntt.co.jp>
      Cc: Gleb Natapov <gleb@redhat.com>
      Cc: Jason Wang <jasowang@redhat.com>
      Cc: Jesper Nilsson <jesper.nilsson@axis.com>
      Cc: Jiri Kosina <jkosina@suse.cz>
      Cc: Jiri Olsa <jolsa@redhat.com>
      Cc: Jiri Slaby <jslaby@suse.cz>
      Cc: Johannes Weiner <hannes@cmpxchg.org>
      Cc: Jonathan Lebon <jlebon@redhat.com>
      Cc: Kees Cook <keescook@chromium.org>
      Cc: Matt Fleming <matt.fleming@intel.com>
      Cc: Michel Lespinasse <walken@google.com>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
      Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
      Cc: Rusty Russell <rusty@rustcorp.com.au>
      Cc: Seiji Aguchi <seiji.aguchi@hds.com>
      Cc: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
      Cc: Tejun Heo <tj@kernel.org>
      Cc: Vineet Gupta <vgupta@synopsys.com>
      Signed-off-by: NIngo Molnar <mingo@kernel.org>
      9326638c
    • M
      kprobes/x86: Allow probe on some kprobe preparation functions · 7ec8a97a
      Masami Hiramatsu 提交于
      There is no need to prohibit probing on the functions
      used in preparation phase. Those are safely probed because
      those are not invoked from breakpoint/fault/debug handlers,
      there is no chance to cause recursive exceptions.
      
      Following functions are now removed from the kprobes blacklist:
      
      	can_boost
      	can_probe
      	can_optimize
      	is_IF_modifier
      	__copy_instruction
      	copy_optimized_instructions
      	arch_copy_kprobe
      	arch_prepare_kprobe
      	arch_arm_kprobe
      	arch_disarm_kprobe
      	arch_remove_kprobe
      	arch_trampoline_kprobe
      	arch_prepare_kprobe_ftrace
      	arch_prepare_optimized_kprobe
      	arch_check_optimized_kprobe
      	arch_within_optimized_kprobe
      	__arch_remove_optimized_kprobe
      	arch_remove_optimized_kprobe
      	arch_optimize_kprobes
      	arch_unoptimize_kprobe
      
      I tested those functions by putting kprobes on all
      instructions in the functions with the bash script
      I sent to LKML. See:
      
        https://lkml.org/lkml/2014/3/27/33Signed-off-by: NMasami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
      Cc: Jiri Kosina <jkosina@suse.cz>
      Cc: Jonathan Lebon <jlebon@redhat.com>
      Link: http://lkml.kernel.org/r/20140417081747.26341.36065.stgit@ltc230.yrl.intra.hitachi.co.jpSigned-off-by: NIngo Molnar <mingo@kernel.org>
      7ec8a97a
  2. 07 8月, 2013 1 次提交
  3. 19 7月, 2013 2 次提交
  4. 22 1月, 2013 1 次提交
  5. 06 3月, 2012 1 次提交