On Tue, Jan 14, 2020 at 03:30:53PM -0500, Qian Cai wrote: > > > > 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. Whew!!! ;-) > > 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. Understood. But there are likely to be other issues with KCSAN, given how new it is. Yes, yes, I certainly would like to believe that the patches we currently know about will make KCSAN perfect for distros, I have way too much grey hair (and too little hair as well!) to really beleive that. As an alternative, once the patches needed for your tests to pass reach mainline, you could announce that KCSAN was ready to be enabled in distros. Though I confess that I don't know how that works. Is there a separate testing kernel binary provided by the distros in question? Thanx, Paul
