syzbot


BUG: rwlock bad magic on CPU, kworker/0:LINE/NUM, ADDR

Status: auto-closed as invalid on 2021/03/26 10:18
Subsystems: tipc
[Documentation on labels]
Reported-by: syzbot+cb987a9c796abc570b47@syzkaller.appspotmail.com
First crash: 1209d, last: 1209d
Discussions (1)
Title Replies (including bot) Last reply
BUG: rwlock bad magic on CPU, kworker/0:LINE/NUM, ADDR 1 (2) 2020/11/30 11:35

Sample crash report:
tipc: 32-bit node address hash set to aa1414ac
BUG: rwlock bad magic on CPU#0, kworker/0:18/18158, 00000000859f2a8d
CPU: 0 PID: 18158 Comm: kworker/0:18 Not tainted 5.10.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events tipc_net_finalize_work
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x107/0x163 lib/dump_stack.c:118
 rwlock_bug kernel/locking/spinlock_debug.c:144 [inline]
 debug_write_lock_before kernel/locking/spinlock_debug.c:182 [inline]
 do_raw_write_lock+0x1ef/0x280 kernel/locking/spinlock_debug.c:206
 tipc_mon_reinit_self+0x1f7/0x630 net/tipc/monitor.c:685
 tipc_net_finalize net/tipc/net.c:134 [inline]
 tipc_net_finalize+0x1df/0x310 net/tipc/net.c:125
 process_one_work+0x933/0x15a0 kernel/workqueue.c:2272
 worker_thread+0x64c/0x1120 kernel/workqueue.c:2418
 kthread+0x3af/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/11/26 10:17 net-old 90cf87d16bd5 2f1cec62 .config console log report info ci-upstream-net-this-kasan-gce
* Struck through repros no longer work on HEAD.