From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>,
Tom Zanussi <zanussi@kernel.org>
Subject: Re: [PATCH 2/2] tracing: Update to the event probes
Date: Fri, 6 Aug 2021 16:55:16 -0400 [thread overview]
Message-ID: <20210806165516.370c1f26@oasis.local.home> (raw)
In-Reply-To: <20210716000406.27c22e3a@oasis.local.home>
On Fri, 16 Jul 2021 00:04:06 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Also, we must make it where writing into the event's trigger files does
> not touch these triggers (as we saw that will crash the system!).
Tzvetomir,
I know I was able to crash the kernel before, but I do not remember how
I did it, and trying various things, I have not been able to crash it
with these patches.
I may continue to try a little more, otherwise, I'll just stop and go
ahead and review your latest patch.
-- Steve
prev parent reply other threads:[~2021-08-06 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 3:26 [PATCH 0/2] tracing: addition of event probe Steven Rostedt
2021-07-16 3:26 ` [PATCH 1/2] Add new kprobe on tracepoint Steven Rostedt
2021-07-16 3:26 ` [PATCH 2/2] tracing: Update to the event probes Steven Rostedt
2021-07-16 4:04 ` Steven Rostedt
2021-08-06 20:55 ` Steven Rostedt [this message]
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=20210806165516.370c1f26@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@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 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).