From: Chunyu Hu <chuhu@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix oops caused by graph notrace filter
Date: Thu, 23 Jun 2016 10:58:55 -0400 (EDT) [thread overview]
Message-ID: <648023723.4701653.1466693935773.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160623103920.36195c3a@gandalf.local.home>
----- Original Message -----
> From: "Steven Rostedt" <rostedt@goodmis.org>
> To: "Chunyu Hu" <chuhu@redhat.com>
> Cc: linux-kernel@vger.kernel.org
> Sent: Thursday, June 23, 2016 10:39:20 PM
> Subject: Re: [PATCH] tracing: Fix oops caused by graph notrace filter
>
> On Thu, 23 Jun 2016 10:20:31 -0400 (EDT)
> Chunyu Hu <chuhu@redhat.com> wrote:
>
> > I tried the patch, if just for resolving the oops issue, it's indeed
> > enough.
> > But if we care about just this filter, and compare this with the
> > trace_graph_entry
> > filter handling, I found that, the depth 0 item will be submitted to the
> > ring buffer, not
> > respecting the filter. I still use the same steps. It's possible to show
> > schedule entry:
>
> Sure, I just wanted to make sure nothing got off, and made the quick
> patch.
>
> Want to send an updated patch that goes this route? That is, make it
> such that the latency tracers fully support the set_graph_notrace.
Sure, if your time allowing me to send it tomorrow, If not, feel free
to fix it as your way.
> -- Steve
>
>
--
Regards,
Chunyu Hu
next prev parent reply other threads:[~2016-06-23 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 10:57 [PATCH] tracing: Fix oops caused by graph notrace filter Chunyu Hu
2016-06-21 12:22 ` kbuild test robot
2016-06-21 12:39 ` kbuild test robot
2016-06-22 5:33 ` Chunyu Hu
2016-06-22 13:08 ` Steven Rostedt
2016-06-23 14:20 ` Chunyu Hu
2016-06-23 14:39 ` Steven Rostedt
2016-06-23 14:58 ` Chunyu Hu [this message]
2016-06-23 15:11 ` Steven Rostedt
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=648023723.4701653.1466693935773.JavaMail.zimbra@redhat.com \
--to=chuhu@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.