syzbot


INFO: trying to register non-static key in update_defense_level

Status: auto-closed as invalid on 2021/01/04 08:37
Subsystems: lvs
[Documentation on labels]
Reported-by: syzbot+80eac45c3b92882289f6@syzkaller.appspotmail.com
First crash: 1328d, last: 1328d
Discussions (1)
Title Replies (including bot) Last reply
INFO: trying to register non-static key in update_defense_level 0 (1) 2020/09/07 21:19

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: 0 PID: 607 Comm: kworker/0:12 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_long defense_work_handler
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x198/0x1fd lib/dump_stack.c:118
 assign_lock_key kernel/locking/lockdep.c:894 [inline]
 register_lock_class+0x157d/0x1630 kernel/locking/lockdep.c:1206
 __lock_acquire+0xf9/0x5570 kernel/locking/lockdep.c:4305
 lock_acquire+0x1f3/0xae0 kernel/locking/lockdep.c:5006
 __raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:151
 spin_lock include/linux/spinlock.h:354 [inline]
 update_defense_level+0xdc/0x10f0 net/netfilter/ipvs/ip_vs_ctl.c:113
 defense_work_handler+0x25/0xe0 net/netfilter/ipvs/ip_vs_ctl.c:235
 process_one_work+0x94c/0x1670 kernel/workqueue.c:2269
 worker_thread+0x64c/0x1120 kernel/workqueue.c:2415
 kthread+0x3b5/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/09/06 08:36 upstream 9322c47b21b9 abf9ba4f .config console log report ci-upstream-kasan-gce
* Struck through repros no longer work on HEAD.