On 10/23/2014 02:39 PM, Paul E. McKenney wrote: > On Tue, Oct 14, 2014 at 10:35:10PM -0400, Sasha Levin wrote: >> On 10/13/2014 01:35 PM, Dave Jones wrote: >>> oday in "rcu stall while fuzzing" news: >>> >>> INFO: rcu_preempt detected stalls on CPUs/tasks: >>> Tasks blocked on level-0 rcu_node (CPUs 0-3): P766 P646 >>> Tasks blocked on level-0 rcu_node (CPUs 0-3): P766 P646 >>> (detected by 0, t=6502 jiffies, g=75434, c=75433, q=0) >> >> I've complained about RCU stalls couple days ago (in a different context) >> on -next. I guess whatever causing them made it into Linus's tree? >> >> https://lkml.org/lkml/2014/10/11/64 > > And on that one, I must confess that I don't see where the RCU read-side > critical section might be. > > Hmmm... Maybe someone forgot to put an rcu_read_unlock() somewhere. > Can you reproduce this with CONFIG_PROVE_RCU=y?
Paul, if that was directed to me - Yes, I see stalls with CONFIG_PROVE_RCU set and nothing else is showing up before/after that. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/