On Tue, 2 Dec 2014 09:04:07 -0800 "Paul E. McKenney" <paul...@linux.vnet.ibm.com> wrote:
> Is it harder to reproduce with CONFIG_PREEMPT=y and CONFIG_TREE_PREEMPT_RCU=n? Yes, it's much harder! :) > If it is a -lot- harder to reproduce, it might be worth bisecting among > the RCU read-side critical sections. If making a few of them be > non-preemptible greatly reduces the probability of the bug occuring, > that might provide a clue about root cause. > > On the other hand, if it is just a little harder to reproduce, this > RCU read-side bisection would likely be an exercise in futility. Ok, I want to bisect it. Since it could be painful to bisect, could you suggest 2 commits between 3.16.0 and 3.17.0 so we can narrow the bisect? I could just bisect between 3.16.0 and 3.17.0 but it would take many days :). Ps: if you prefer I bisect between 3.16.0 and 3.17.0, no problem, but you'll have to be patient ;). -- Linux 3.17.0-dirty: Shuffling Zombie Juror http://www.youtube.com/DanielFragaBR http://exchangewar.info Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL -- 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/