linux-kernel - Re: There is a Tasks RCU stall warning

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: <20170411173447.0bdb9f77@gandalf.local.home>
Date:   Tue, 11 Apr 2017 17:34:47 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: There is a Tasks RCU stall warning

On Tue, 11 Apr 2017 17:31:33 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> The thread gets created when I enable the benchmark tracepoint. It just
> so happens that my test enables *all* tracepoints, which would of
> course include this one as well.
> 
> I'll have to look at this code to see why it is getting missed.

Yep, this thread never goes to sleep, but will call cond_resched()
periodically. This keeps rcu_tasks() from finishing.

Should I add a direct "schedule()" in there instead of a
cond_resched(), or do you think rcu_tasks should have cond_resched() be
a quiescent state as well?

-- Steve