hi, Paul,
On Tue, Dec 24, 2024 at 09:57:16AM -0800, Paul E. McKenney wrote:
> On Tue, Dec 24, 2024 at 02:48:26PM +0800, kernel test robot wrote:
> >
> > hi, Paul,
> >
> > we noticed there is similar commit in newer branches:
> > dev.2024.12.11b
> > dev.2024.12.12a
> > dev.2024.12.13a
> >
> > if this is out-of-date version, please just ignore.
> >
> > the new config is enabled in our tests.
> > ==================== PARENT FIRST_BAD KCONFIGS bb02a67f70d8d58c675403f1f716cf5885967918 ====================
> > --- /pkg/linux/i386-randconfig-001-20241220/clang-19/bb02a67f70d8d58c675403f1f716cf5885967918/.config 2024-12-23 12:46:05.807021581 +0800
> > +++ /pkg/linux/i386-randconfig-001-20241220/clang-19/774c4d7adb4f9134aa265c5fee4e8b07d98c53cb/.config 2024-12-23 14:26:59.938500419 +0800
> > @@ -5864,6 +5864,7 @@ CONFIG_PROVE_RCU=y
> > CONFIG_TORTURE_TEST=m
> > CONFIG_RCU_SCALE_TEST=m
> > CONFIG_RCU_TORTURE_TEST=m
> > +CONFIG_RCU_TORTURE_TEST_CHK_RDR_STATE=m
> > # CONFIG_RCU_TORTURE_TEST_LOG_CPU is not set
> > CONFIG_RCU_REF_SCALE_TEST=m
> > CONFIG_RCU_CPU_STALL_TIMEOUT=21
> >
> >
> > and since the WARN added in this commit is hit, we just make below report FYI.
>
> This one is a bug that has since been fixed. The condition:
>
> cur_ops->readlock_nesting() > 0
>
> Now reads:
>
> cur_ops->readlock_nesting() == 0
>
> The updated commit is:
>
> 14f8cc687ce6 ("rcutorture: Make rcutorture_one_extend() check reader state")
>
> However, your Kconfig above does in fact show a bug. It is supposed
> to be bool rather than tristate. I will fix with your Reported-by.
thanks a lot for information! always our great pleasure that our report is
helpful :)
>
> Thanx, Paul
