WARNING in rcu_process_callbacks
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · syzbot
Hello,
syzkaller hit the following crash on
6084b576dca2e898f5c101baef151f7bfdbb606dgit://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
Quoted 8 lines
Unfortunately, I don't have any reproducer for this bug yet.
RBP:
00007f50826f4a90R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12:00000000004b75bb
R13:00007f50826f4bc8R14:00000000004b75bbR15: 0000000000000000WARNING: CPU: 0 PID: 7719 at kernel/rcu/tree.c:2714 arch_local_irq_disable
arch/x86/include/asm/paravirt.h:772[inline]
So the only thing which triggers a BUG in that code is the paravirt stuff
#define PVOP_TEST_NULL(op) BUG_ON(op == NULL)
Your config has PARAVIRT_DEBUG=y
So this is again something which got executed before a gazillion of times and then something becomes NULL. In this case it's pv_irq_ops.irq_disable
I've seen such unexplainable NULL pointers in quite some sysbot bug reports lately. The irq_desc->irq_data.common issue is more or less the same problem. This really stinks like a stray pointer.
Thanks,
tglx