> On Jan 14, 2020, at 2:22 PM, Paul E. McKenney <paulmck@xxxxxxxxxx> wrote: > > Just so I understand... Does this problem happen even in CONFIG_KCSAN=n > kernels? No. > > I have been running extensive CONFIG_KSCAN=y rcutorture tests for quite > awhile now, so even if this only happens for CONFIG_KSCAN=y, it is not > like it affects everyone. > > Yes, it should be fixed, and Marco does have a patch on the way. The concern is really about setting KSCAN=y in a distro debug kernel where it has other debug options. I’ll try to dig into more of those issues in the next few days.
