public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org>
Cc: x86@kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
	Yang Bo <yangbo@deepin.com>, Ingo Molnar <mingo@redhat.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org,
	Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Laura Abbott <labbott@redhat.com>, Josef Bacik <jbacik@fb.com>,
	Alexei Starovoitov <ast@kernel.org>
Subject: [PATCH -tip v2 0/5] kprobes: x86: Cleanup jprobe implementation on x86
Date: Mon, 12 Mar 2018 23:40:55 +0900	[thread overview]
Message-ID: <152086565510.32679.6953754320525763743.stgit@devbox> (raw)

Hello,

Since we decided to remove jprobe from kernel last year,
its APIs are disabled and we worked on moving in-kernel
jprobe users to kprobes or trace-events. And now no jprobe
users are here anymore.

This series removes jprobe implementation from x86 and
generic code. I would like to send other series for each
arch. After all those patches are merged, I will remove
jprobes APIs and data structures, since changing those
definitions will break build on other archs.

Here is the series of patches to show how to do that.
I've dropped arch-independent header changes from this
version and merged kprobe-user code changes into the
last patch since that changed the kprobes expected
behavior when the kprobes modifies execution path.
(no need to enable preempt anymore)

 - Remove jprobe functions (register/unregister,
   setjump/longjump) from generic/arch-dependent code.
   [1/5][2/5]
 - Remove break_handler related code.
   [3/5][4/5]
 - Do not disable preemption on exception handler
   [5/5]

As I said above, the last patch [5/5] will change the
expected behavior on x86. Other archs also have to change
it. But anyway, currently such execution-path modifying
users in tree are very limited and only works on x86.
So we can safely modify it.

Thank you,

---

Masami Hiramatsu (5):
      kprobes: Remove jprobe API implementation
      x86: kprobes: Remove jprobe implementation
      kprobes: Ignore break_handler
      x86: kprobes: Ignore break_handler
      x86: kprobes: Do not disable preempt on int3 path


 Documentation/kprobes.txt        |   13 ++--
 arch/x86/include/asm/kprobes.h   |    3 -
 arch/x86/kernel/kprobes/common.h |   10 ---
 arch/x86/kernel/kprobes/core.c   |  114 ++------------------------------------
 arch/x86/kernel/kprobes/ftrace.c |   21 +------
 arch/x86/kernel/kprobes/opt.c    |    1 
 include/linux/kprobes.h          |    3 -
 kernel/fail_function.c           |    1 
 kernel/kprobes.c                 |  115 ++------------------------------------
 kernel/trace/trace_kprobe.c      |    3 -
 10 files changed, 20 insertions(+), 264 deletions(-)

--
Masami Hiramatsu (Linaro)

             reply	other threads:[~2018-03-12 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 14:40 Masami Hiramatsu [this message]
2018-03-12 14:41 ` [PATCH -tip v2 1/5] kprobes: Remove jprobe API implementation Masami Hiramatsu
2018-03-12 14:41 ` [PATCH -tip v2 2/5] x86: kprobes: Remove jprobe implementation Masami Hiramatsu
2018-03-12 14:42 ` [PATCH -tip v2 3/5] kprobes: Ignore break_handler Masami Hiramatsu
2018-03-12 14:42 ` [PATCH -tip v2 4/5] x86: " Masami Hiramatsu
2018-03-12 14:43 ` [PATCH -tip v2 5/5] x86: kprobes: Do not disable preempt on int3 path Masami Hiramatsu
2018-05-16  7:00 ` [PATCH -tip v2 0/5] kprobes: x86: Cleanup jprobe implementation on x86 Masami Hiramatsu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=152086565510.32679.6953754320525763743.stgit@devbox \
    --to=mhiramat@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=ast@kernel.org \
    --cc=hpa@zytor.com \
    --cc=jbacik@fb.com \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yangbo@deepin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox