linux-kernel - Re: [for-next][PATCH 1/5] tracepoint: Give priority to probes of tracepoints

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]

Message-ID: <20151030162537.6409d174@gandalf.local.home>
Date:	Fri, 30 Oct 2015 16:25:37 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [for-next][PATCH 1/5] tracepoint: Give priority to probes of
 tracepoints

On Thu, 29 Oct 2015 17:52:16 +0000 (UTC)
Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote:

> ----- On Oct 29, 2015, at 3:07 AM, rostedt rostedt@...dmis.org wrote:
> 
> > From: "Steven Rostedt (Red Hat)" <rostedt@...dmis.org>
> > 
> > In order to guarantee that a probe will be called before other probes that
> > are attached to a tracepoint, there needs to be a mechanism to provide
> > priority of one probe over the others.
> > 
> > Adding a prio field to the struct tracepoint_func, which lets the probes be
> > sorted by the priority set in the structure. If no priority is specified,
> > then a priority of 10 is given (this is a macro, and perhaps may be changed
> > in the future).
> > 
> > Now probes may be added to affect other probes that are attached to a
> > tracepoint with a guaranteed order.
> > 
> > One use case would be to allow tracing of tracepoints be able to filter by
> > pid. A special (higher priority probe) may be added to the sched_switch
> > tracepoint and set the necessary flags of the other tracepoints to notify
> > them if they should be traced or not. In case a tracepoint is enabled at the
> > sched_switch tracepoint too, the order of the two are not random.
> > 
> > Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
> 
> Sounds good to me,
> 
> Acked-by: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
> 

Thanks.

Unfortunately I already pushed it out to linux-next (had a deadline),
otherwise I could have added your ack. I'm guessing you missed the RFC
version I posted a week ago.

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/