On Mon, Mar 30, 2020 at 2:43 AM Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx> wrote: > > Hi Tetsuo and Dmitry, thanks for noticing this Tetsuo. And sorry for > not looping you in the patch Dmitry, I wasn't aware that you were > working with testing. By the way, I suggest people interested in linux > testing to create a ML; I'd be glad to have looped such list, but I > couldn't find information about a group dealing with testing. > > So Tetsuo, you got it right: just change it to > "sysctl.kernel.hung_task_all_cpu_backtrace=1" and that should work > fine, once Vlastimil's patch gets merged (and I hope it happens soon). > Cheers, > > > Guilherme +LKML, workflows, syzkaller, kernelci, cki, kbuild Tetsuo, thanks for notifying again. Yes, kernel devs breaking all testing happens from time to time and currently there is no good way to address this. Other things I remember is the introduction of CONFIG_DEBUG_MEMORY, which defaults to =n and disables KASAN, which in turn produced an explosion of assorted crashes caused by memory corruptions; also periodic changes in kernel crash messages which I assume all testing systems parse and need to understand. Is there already a mailing list for this? Or should we create one? I.e. announce and changes that may need actions from all testing systems. Another thing that may benefit from announcements is addition of new useful debugging configs. Currently they are introduced silently and don't reach the target audience.
