linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, mhiramat@kernel.org, mingo@redhat.com
Subject: [PATCH 0/3] tracing/probe: Fix some issues on multiprobe support
Date: Wed, 18 Sep 2019 17:55:28 +0900	[thread overview]
Message-ID: <156879692790.31056.9404391078827158266.stgit@devnote2> (raw)

Hi Steve,

Here are the patches to fix some issues on multiprobe support
(and add a testcase for the fix)

 [1/3] Fix to allow user to enable probe events on unloaded modules.
       This was supported before multiprobe support. Fix it.

 [2/3] Reject exactly same probe event. Multiprobe accepts the exact
       same probe as existing one, but it is meansingless and confusing.
       Reject the probe events which has exact same probe point and same
       arguments.

 [3/3] Add a testcase for [2/3].

Thank you,

---

Masami Hiramatsu (3):
      tracing/probe: Fix to allow user to enable events on unloaded modules
      tracing/probe: Reject exactly same probe event
      selftests/ftrace: Update kprobe event error testcase


 kernel/trace/trace_kprobe.c                        |   69 ++++++++++++++------
 kernel/trace/trace_probe.h                         |    3 +
 kernel/trace/trace_uprobe.c                        |   52 +++++++++++++--
 .../ftrace/test.d/kprobe/kprobe_syntax_errors.tc   |    1 
 4 files changed, 96 insertions(+), 29 deletions(-)

--
Masami Hiramatsu <mhiramat@kernel.org>

             reply	other threads:[~2019-09-18  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18  8:55 Masami Hiramatsu [this message]
2019-09-18  8:55 ` [PATCH 1/3] tracing/probe: Fix to allow user to enable events on unloaded modules Masami Hiramatsu
2019-09-18  8:55 ` [PATCH 2/3] tracing/probe: Reject exactly same probe event Masami Hiramatsu
2019-09-18  8:55 ` [PATCH 3/3] selftests/ftrace: Update kprobe event error testcase 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=156879692790.31056.9404391078827158266.stgit@devnote2 \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    /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;
as well as URLs for NNTP newsgroup(s).