syzbot


INFO: trying to register non-static key in neigh_periodic_work

Status: auto-closed as invalid on 2021/08/20 05:05
Reported-by: syzbot+4c79bfd3ac30dbddd0ca@syzkaller.appspotmail.com
First crash: 433d, last: 433d

Sample crash report:
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 2127 Comm: kworker/1:18 Not tainted 4.14.231-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_power_efficient neigh_periodic_work
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 register_lock_class+0x32b/0x1320 kernel/locking/lockdep.c:768
 __lock_acquire+0x167/0x3f20 kernel/locking/lockdep.c:3378
 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
 __raw_write_lock include/linux/rwlock_api_smp.h:210 [inline]
 _raw_write_lock+0x2a/0x40 kernel/locking/spinlock.c:296
 neigh_periodic_work+0x27b/0x8b0 net/core/neighbour.c:826
 process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
ufs: ufs was compiled with read-only support, can't be mounted as read-write

Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-linux-4-14 2021/04/22 05:05 linux-4.14.y cf256fbcbe34 2bc8999a .config log report info INFO: trying to register non-static key in neigh_periodic_work