Hello, Paul! > > > > > > > > > > Except that I got this from overnight testing of rcu/dev on the shared > > > > > RCU tree: > > > > > > > > > > WARNING: CPU: 5 PID: 14 at kernel/rcu/tree.c:1636 > > > > > rcu_sr_normal_complete+0x5c/0x80 > > > > > > > > > > I see this only on TREE05. Which should not be too surprising, given > > > > > that this is the scenario that tests it. It happened within five > > > > > minutes > > > > > on all 14 of the TREE05 runs. > > > > > > > > > Hm.. This is not fun. I tested this on my system and i did not manage to > > > > trigger this whereas you do. Something is wrong. > > > > > > If you have a debug patch, I would be happy to give it a go. > > > > > I can trigger it. But. > > > > Some background. I tested those patches during many hours on the stable > > kernel which is 6.13. On that kernel i was not able to trigger it. Running > > the rcutorture on the our shared "dev" tree, which i did now, triggers this > > right away. > > Bisection? (Hey, you knew that was coming!) > Looks like this: rcu: Fix get_state_synchronize_rcu_full() GP-start detection
After revert in the dev, rcutorture passes TREE05, 16 instances. -- Uladzislau Rezki
