hi, Z qiang, On Mon, Aug 19, 2024 at 05:11:44PM +0800, Z qiang wrote: > > > > > > hi, Paul, > > > > we actually want to consult you about this patch. by it, the config has below > > diff with parent in this tests (we use randconfig here) > > > > --- /pkg/linux/i386-randconfig-004-20240810/gcc-12/157f4b896656dfe6ad6d37c94ca9a885d52f35ab/.config 2024-08-12 04:00:50.715727095 +0800 > > +++ /pkg/linux/i386-randconfig-004-20240810/gcc-12/a7adbae9c55d7f85b3b8c0e8e9417e5d52793137/.config 2024-08-12 04:02:38.647990561 +0800 > > @@ -136,7 +136,7 @@ CONFIG_BSD_PROCESS_ACCT_V3=y > > CONFIG_TREE_RCU=y > > CONFIG_PREEMPT_RCU=y > > CONFIG_RCU_EXPERT=y > > -CONFIG_TREE_SRCU=y > > +CONFIG_TINY_SRCU=y > > CONFIG_TASKS_RCU_GENERIC=y > > CONFIG_FORCE_TASKS_RCU=y > > CONFIG_NEED_TASKS_RCU=y > > > > > > then we saw issue show for this commit: > > > > 157f4b896656dfe6 a7adbae9c55d7f85b3b8c0e8e94 > > ---------------- --------------------------- > > fail:runs %reproduction fail:runs > > | | | > > :6 67% 6:6 rcutorture.busted_srcud.fail > > :6 83% 6:6 dmesg.EIP:rcu_torture_stats_print > > :6 83% 6:6 dmesg.WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print[rcutorture] > > > > > > another diff is, for parent, we can see: > > > > [ 465.948962] busted_srcud-torture:--- End of test: SUCCESS: nreaders=1 nfakewriters=4 stat_interval=60 verbose=1 test_no_idle_hz=1 shuffle_interval=3 stutter=5 irqreader=1 fqs_duration=0 fqs_holdoff=0 fqs_stutter=3 test_boost=1/0 test_boost_interval=7 test_boost_duration=4 shutdown_secs=0 stall_cpu=0 stall_cpu_holdoff=10 stall_cpu_irqsoff=0 stall_cpu_block=0 stall_cpu_repeat=0 n_barrier_cbs=0 onoff_interval=0 onoff_holdoff=0 read_exit_delay=13 read_exit_burst=16 nocbs_nthreads=0 nocbs_toggle=1000 test_nmis=0 > > > > > > but for this commit: > > > > > > [ 417.566774] busted_srcud-torture:--- End of test: FAILURE: nreaders=1 nfakewriters=4 stat_interval=60 verbose=1 test_no_idle_hz=1 shuffle_interval=3 stutter=5 irqreader=1 fqs_duration=0 fqs_holdoff=0 fqs_stutter=3 test_boost=1/0 test_boost_interval=7 test_boost_duration=4 shutdown_secs=0 stall_cpu=0 stall_cpu_holdoff=10 stall_cpu_irqsoff=0 stall_cpu_block=0 stall_cpu_repeat=0 n_barrier_cbs=0 onoff_interval=0 onoff_holdoff=0 read_exit_delay=13 read_exit_burst=16 nocbs_nthreads=0 nocbs_toggle=1000 test_nmis=0 > > > > > > are these expected? below full report FYI. > > > Due to setting ->extendables=RCUTORTURE_MAX_EXTEND for busted_srcud testing, > they use abnormal reader critical sections, this is expected > behavior. not a problem. got it. thanks a lot for information.
