All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Tom Zanussi <zanussi@kernel.org>,
	Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
	Yordan Karadzhov <y.karadz@gmail.com>
Subject: [PATCH v2 0/2] tracing: Fix removal of eprobes and add test
Date: Wed, 13 Oct 2021 16:51:11 -0400	[thread overview]
Message-ID: <20211013205111.587708359@goodmis.org> (raw)

When doing the following:

 # echo 'e:hrstate timer/hrtimer_cancel state=+0x38($hrtimer):u8' >> dynamic_events

 # echo '-:hrstate timer/hrtimer_cancel state=+0x38($hrtimer):u8' >> dynamic_events

It errors out with -ENOENT. This is because the "match" function does not
take into account the "timer/hrtimer_cancel" part. Fix it and also make it
work more genericly like kprobes and uprobes.

v1 at: https://lore.kernel.org/all/20211013234206.37dd18ffcc2a2cbf4493f125@kernel.org/

Changes since v1:
 - Instead of just fixing the missing system/event, have it be more like
   kprobes and uprobes.

Steven Rostedt (VMware) (2):
      tracing: Fix event probe removal from dynamic events
      selftests/ftrace: Update test for more eprobe removal process

----
 kernel/trace/trace_eprobe.c                        | 54 ++++++++++++++++++++--
 .../ftrace/test.d/dynevent/add_remove_eprobe.tc    | 54 +++++++++++++++++++++-
 2 files changed, 103 insertions(+), 5 deletions(-)

             reply	other threads:[~2021-10-13 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 20:51 Steven Rostedt [this message]
2021-10-13 20:51 ` [PATCH v2 1/2] tracing: Fix event probe removal from dynamic events Steven Rostedt
2021-10-13 20:51 ` [PATCH v2 2/2] selftests/ftrace: Update test for more eprobe removal process Steven Rostedt
2021-10-13 23:16 ` [PATCH v2 0/2] tracing: Fix removal of eprobes and add test 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=20211013205111.587708359@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=tz.stoyanov@gmail.com \
    --cc=y.karadz@gmail.com \
    --cc=zanussi@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.