Re: [for-next][PATCH 09/18] tracing: Move pipe reference to trace array instead of current_tracer

2020-07-31 Thread dann frazier
On Fri, Jul 31, 2020 at 3:16 PM Steven Rostedt wrote: > > On Fri, 31 Jul 2020 13:33:45 -0600 > dann frazier wrote: > > > > This is marked as "Fixes" but is more of a clean up than a true fix. > > > Backport if you want, but its not critical. > > > > Thanks Steven! In case it helps backport

Re: [for-next][PATCH 09/18] tracing: Move pipe reference to trace array instead of current_tracer

2020-07-31 Thread Steven Rostedt
On Fri, 31 Jul 2020 13:33:45 -0600 dann frazier wrote: > > This is marked as "Fixes" but is more of a clean up than a true fix. > > Backport if you want, but its not critical. > > Thanks Steven! In case it helps backport consideration, I wanted to > note that this addresses an issue we've

Re: [for-next][PATCH 09/18] tracing: Move pipe reference to trace array instead of current_tracer

2020-07-31 Thread dann frazier
On Thu, Jul 02, 2020 at 05:58:21PM -0400, Steven Rostedt wrote: > From: "Steven Rostedt (VMware)" > > If a process has the trace_pipe open on a trace_array, the current tracer > for that trace array should not be changed. This was original enforced by a > global lock, but when instances were

[for-next][PATCH 09/18] tracing: Move pipe reference to trace array instead of current_tracer

2020-07-02 Thread Steven Rostedt
From: "Steven Rostedt (VMware)" If a process has the trace_pipe open on a trace_array, the current tracer for that trace array should not be changed. This was original enforced by a global lock, but when instances were introduced, it was moved to the current_trace. But this structure is shared