Re: [PATCH v9 35/37] tracing: Increase trace_recursive_lock() limit for synthetic events

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Steve,

On Wed, 2018-02-07 at 20:55 -0500, Steven Rostedt wrote:
> On Mon, 15 Jan 2018 20:52:09 -0600
> Tom Zanussi <tom.zanussi@xxxxxxxxxxxxxxx> wrote:
> 
> >  static __always_inline int
> >  trace_recursive_lock(struct ring_buffer_per_cpu *cpu_buffer)
> >  {
> > -	if (cpu_buffer->current_context >= 4)
> > +	if (cpu_buffer->current_context >= 6)
> 
> I can't apply this patch because the new context counting broke tracing
> suspend and resume because it depended on the context recursive locking.
> 
> Link: http://lkml.kernel.org/r/20180116020051.776011914@xxxxxxxxxxx
> 
> I added the attached two patches which appear to do the job.
> 
> Let me know what you think.
> 

Yeah, these look good and seem to do the trick - I did some quick
testing and didn't see any problems.

Thanks,

Tom


--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux