linux-kernel - Re: RCU stall when using function

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: <20170801201214.1e9c7d8e@gandalf.local.home>
Date:   Tue, 1 Aug 2017 20:12:14 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:     paulmck@...ux.vnet.ibm.com, john.stultz@...aro.org,
        linux-kernel@...r.kernel.org
Subject: Re: RCU stall when using function_graph

On Wed, 2 Aug 2017 00:15:44 +0200
Daniel Lezcano <daniel.lezcano@...aro.org> wrote:

> On 02/08/2017 00:04, Paul E. McKenney wrote:
> >> Hi Paul,
> >>
> >> I have been trying to set the function_graph tracer for ftrace and each time I
> >> get a CPU stall.
> >>
> >> How to reproduce:
> >> -----------------
> >>
> >> 		 echo function_graph > /sys/kernel/debug/tracing/current_tracer
> >>
> >> This error appears with v4.13-rc3 and v4.12-rc6.

Can you bisect this? It may be due to this commit:

0598e4f08 ("ftrace: Add use of synchronize_rcu_tasks() with dynamic trampolines")

-- Steve

> >>
> >> Is it something already reported ?  
> > 
> > I have seen this sort of thing, but only when actually dumping the trace
> > out, and I though those got fixed.  You are seeing this just accumulating
> > the trace?  
> 
> No, just by changing the tracer. It is the first operation I do after
> rebooting and it is reproducible each time. That happens on an ARM64
> platform.
> 
> > These RCU CPU stall warnings usually occur when something grabs hold of
> > a CPU for too long, as in 21 seconds or so.  One way that they can happen
> > is excessive lock contention, another is having the kernel run through
> > too much data at one shot.
> > 
> > Adding Steven Rostedt on CC for his thoughts.
> > 
>