linux-kernel - Re: [PATCH] tracing: Fix oops caused by graph notrace filter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Jun 2016 10:58:55 -0400 (EDT)
From:	Chunyu Hu <chuhu@...hat.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing: Fix oops caused by graph notrace filter



----- Original Message -----
> From: "Steven Rostedt" <rostedt@...dmis.org>
> To: "Chunyu Hu" <chuhu@...hat.com>
> Cc: linux-kernel@...r.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@...hat.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