From: Steven Rostedt <rostedt@goodmis.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Ming Lei <tom.leiming@gmail.com>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: kprobe: __blkdev_put probe is missed
Date: Fri, 19 Jun 2020 08:19:54 -0400 [thread overview]
Message-ID: <20200619081954.3d72a252@oasis.local.home> (raw)
In-Reply-To: <20200619072859.GA205278@T590>
On Fri, 19 Jun 2020 15:28:59 +0800
Ming Lei <ming.lei@redhat.com> wrote:
> >
> > OK, then let's make events (for sure)
> >
> > root@devnote2:/sys/kernel/debug/tracing# echo p __blkdev_put >> kprobe_events
> > root@devnote2:/sys/kernel/debug/tracing# echo r __blkdev_put >> kprobe_events
> > root@devnote2:/sys/kernel/debug/tracing# echo p blkdev_put >> kprobe_events
Hi Ming,
Do you have the kprobe_events file?
> > root@devnote2:/sys/kernel/debug/tracing# echo 1 > events/kprobes/enable
>
> I can't find 'events/kprobes' in my VM with upstream kernel, also not found
> the dir under fedora31(5.5.15-200) & rhel8(v4.18 based).
The events/kprobes directly will be created when you create a
kprobe_event. It wont exist until then.
-- Steve
next prev parent reply other threads:[~2020-06-19 12:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 10:30 krobe: __blkdev_put probe is missed Ming Lei
2020-06-18 12:54 ` kprobe: " Ming Lei
2020-06-18 13:56 ` Masami Hiramatsu
2020-06-18 23:19 ` Ming Lei
2020-06-19 5:12 ` Masami Hiramatsu
2020-06-19 7:28 ` Ming Lei
2020-06-19 12:19 ` Steven Rostedt [this message]
2020-06-19 13:32 ` Ming Lei
2020-06-19 15:35 ` Masami Hiramatsu
2020-06-19 23:28 ` Ming Lei
2020-06-20 0:59 ` Steven Rostedt
2020-06-20 1:37 ` Masami Hiramatsu
2020-06-22 0:27 ` Ming Lei
2020-06-22 1:34 ` Masami Hiramatsu
2020-06-22 13:01 ` Steven Rostedt
2020-06-22 23:47 ` Masami Hiramatsu
2020-06-23 0:38 ` Masami Hiramatsu
2020-06-23 5:28 ` 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=20200619081954.3d72a252@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=ming.lei@redhat.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=tom.leiming@gmail.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;
as well as URLs for NNTP newsgroup(s).