syzbot


INFO: task hung in linkwatch_event

Status: upstream: reported on 2024/01/11 11:32
Reported-by: syzbot+07cfae8a92c0b83c91de@syzkaller.appspotmail.com
First crash: 110d, last: 43d
Similar bugs (12)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-414 INFO: task hung in linkwatch_event C 7 1627d 1847d 0/1 public: reported C repro on 2019/04/10 16:14
linux-4.14 INFO: task hung in linkwatch_event (2) 1 648d 648d 0/1 auto-obsoleted due to no activity on 2022/11/19 11:58
android-44 INFO: task hung in linkwatch_event 6 2063d 2208d 0/2 auto-closed as invalid on 2019/03/05 13:11
upstream INFO: task hung in linkwatch_event net C 82 1655d 2267d 0/26 closed as dup on 2018/02/14 15:33
linux-4.14 INFO: task hung in linkwatch_event 5 1331d 1458d 0/1 auto-closed as invalid on 2021/01/05 01:42
linux-4.19 INFO: task hung in linkwatch_event (2) C error 217 422d 1511d 0/1 upstream: reported C repro on 2020/03/11 20:12
upstream INFO: task hung in linkwatch_event (2) net C done done 1033 736d 1462d 20/26 fixed on 2022/05/13 11:13
linux-4.19 INFO: task hung in linkwatch_event 3 1664d 1778d 0/1 auto-closed as invalid on 2020/02/07 01:11
upstream INFO: task hung in linkwatch_event (3) net 304 4d04h 525d 0/26 upstream: reported on 2022/11/22 17:04
linux-4.14 INFO: task hung in linkwatch_event (3) 2 482d 483d 0/1 upstream: reported on 2023/01/03 10:49
android-49 INFO: task hung in linkwatch_event 13 1826d 1843d 0/3 auto-closed as invalid on 2019/10/25 08:50
linux-6.1 INFO: task hung in linkwatch_event 2 268d 384d 0/3 auto-obsoleted due to no activity on 2023/11/14 00:59

Sample crash report:
INFO: task kworker/0:6:3563 blocked for more than 143 seconds.
      Not tainted 5.15.152-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:6     state:D stack:23896 pid: 3563 ppid:     2 flags:0x00004000
Workqueue: events linkwatch_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
 __mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 linkwatch_event+0xa/0x50 net/core/link_watch.c:251
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/26:
 #0: ffffffff8c91f720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/u4:1/144:
 #0: ffff888011dcd138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc900010bfd20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8d9cfe50 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:558
 #3: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock_unregistering net/core/dev.c:11576 [inline]
 #3: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: default_device_exit_batch+0x1ac/0x3f0 net/core/dev.c:11614
 #4: ffffffff8c923ce8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
 #4: ffffffff8c923ce8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:845
3 locks held by kworker/1:2/1064:
 #0: ffff888011c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90004e37d20 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:74
3 locks held by kworker/u4:3/1087:
2 locks held by getty/3262:
 #0: ffff88807f039098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002bab2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:5/3559:
 #0: ffff888011c71938 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90002f87d20 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: reg_check_chans_work+0x7f/0xb70 net/wireless/reg.c:2436
3 locks held by kworker/0:6/3563:
 #0: ffff888011c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90002fc7d20 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
4 locks held by kworker/u4:5/3593:
 #0: ffff8881425ba138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90003097d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffff88807f0c6bd8 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1f6/0x3d10 fs/ext4/inode.c:2677
 #3: ffff88807f0d0990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x12b9/0x1570 fs/jbd2/transaction.c:462
3 locks held by kworker/1:10/8716:
 #0: ffff888023cc0138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc9000456fd20 ((addr_chk_work).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0xa/0x20 net/ipv6/addrconf.c:4655
2 locks held by kworker/0:3/17446:
 #0: ffff888011c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc900032b7d20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
2 locks held by syz-executor.3/17940:
3 locks held by syz-executor.3/17946:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff888056c635c8 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff888056c635c8 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.2/18011:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff88803d125da8 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88803d125da8 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.2/18033:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff888056c67198 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff888056c67198 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.1/18040:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff88806f4e5da8 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88806f4e5da8 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.2/18052:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff88803d1117e0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88803d1117e0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.1/18058:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff888042c253b0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff888042c253b0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.1/18090:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff88803a2a2bd0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88803a2a2bd0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.0/18103:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff888059975da8 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff888059975da8 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.1/18118:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff88803a2a7198 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88803a2a7198 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
3 locks held by syz-executor.0/18126:
 #0: ffff88807f0c4460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825
 #1: ffff88803a0f2bd0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff88803a0f2bd0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262
 #2: ffff88807f0c40e0 (&type->s_umount_key#32){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x1d/0xb0 fs/fs-writeback.c:2729
2 locks held by syz-executor.2/18188:
1 lock held by syz-executor.1/18198:
1 lock held by syz-executor.0/18208:
1 lock held by syz-executor.1/18222:
1 lock held by syz-executor.0/18232:
1 lock held by syz-executor.2/18240:
1 lock held by syz-executor.1/18247:
2 locks held by syz-executor.0/18260:
1 lock held by syz-executor.1/18263:
2 locks held by syz-executor.4/18270:
1 lock held by syz-executor.0/18279:
3 locks held by syz-executor.2/18284:
2 locks held by syz-executor.1/18318:
2 locks held by syz-executor.2/18333:
2 locks held by syz-executor.2/18394:
1 lock held by syz-executor.2/18417:
1 lock held by syz-executor.2/18443:
1 lock held by syz-executor.1/18450:
1 lock held by syz-executor.4/18929:
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5626
1 lock held by syz-executor.0/18956:
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5626
1 lock held by syz-executor.2/19207:
2 locks held by syz-executor.3/19242:
1 lock held by syz-executor.1/19289:
1 lock held by syz-executor.2/19326:
1 lock held by syz-executor.2/19342:
1 lock held by syz-executor.2/19360:
3 locks held by syz-executor.2/19392:
1 lock held by syz-executor.4/19447:
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5626
1 lock held by syz-executor.0/19488:
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5626
3 locks held by syz-executor.2/19608:
1 lock held by syz-executor.3/19613:
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: __tun_chr_ioctl+0x460/0x2270 drivers/net/tun.c:3047
1 lock held by syz-executor.3/19617:
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: __tun_chr_ioctl+0x460/0x2270 drivers/net/tun.c:3047
2 locks held by syz-executor.2/19616:
1 lock held by syz-executor.1/19621:
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8d9dba08 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5626
3 locks held by syz-executor.2/19628:
2 locks held by syz-executor.2/19634:
2 locks held by syz-executor.2/19639:
2 locks held by syz-executor.2/19647:
2 locks held by syz-executor.2/19654:
2 locks held by syz-executor.2/19659:
2 locks held by syz-executor.2/19665:
2 locks held by syz-executor.2/19671:
2 locks held by syz-executor.2/19673:

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 26 Comm: khungtaskd Not tainted 5.15.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
 watchdog+0xe72/0xeb0 kernel/hung_task.c:295
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4601 Comm: kworker/u4:8 Not tainted 5.15.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Workqueue: ext4-rsv-conversion ext4_end_io_rsv_work
RIP: 0010:crc_41+0x0/0x1e
Code: ff ff f2 4d 0f 38 f1 93 a8 fe ff ff f2 4c 0f 38 f1 81 b0 fe ff ff f2 4c 0f 38 f1 8a b0 fe ff ff f2 4d 0f 38 f1 93 b0 fe ff ff <f2> 4c 0f 38 f1 81 b8 fe ff ff f2 4c 0f 38 f1 8a b8 fe ff ff f2 4d
RSP: 0018:ffffc90004eaf270 EFLAGS: 00000246
RAX: 000000000000002a RBX: 00000000000003fc RCX: ffff88805166ad50
RDX: ffff88805166aea0 RSI: 00000000000003fc RDI: ffffffff8147e25e
RBP: 0000000000000ffc R08: 0000000059654551 R09: 000000003c1e4e95
R10: 000000003c1e4e95 R11: ffff88805166aff0 R12: ffff88805166a000
R13: dffffc0000000000 R14: 1ffff920009d5e91 R15: 0000000000000ffc
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c00165d010 CR3: 000000001b572000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 crc32c_pcl_intel_update+0x79/0x270 arch/x86/crypto/crc32c-intel_glue.c:162
 crypto_shash_update+0x1db/0x2a0 crypto/shash.c:131
 ext4_chksum fs/ext4/ext4.h:2449 [inline]
 ext4_extent_block_csum fs/ext4/extents.c:56 [inline]
 ext4_extent_block_csum_set+0x368/0x520 fs/ext4/extents.c:84
 __ext4_ext_dirty+0xbe/0x1c0 fs/ext4/extents.c:174
 ext4_convert_unwritten_extents_endio fs/ext4/extents.c:3749 [inline]
 ext4_ext_handle_unwritten_extents fs/ext4/extents.c:3874 [inline]
 ext4_ext_map_blocks+0x39ac/0x7690 fs/ext4/extents.c:4207
 ext4_map_blocks+0xaad/0x1e00 fs/ext4/inode.c:645
 ext4_convert_unwritten_extents+0x2e0/0x6c0 fs/ext4/extents.c:4844
 ext4_convert_unwritten_io_end_vec+0xfd/0x170 fs/ext4/extents.c:4883
 ext4_end_io_end fs/ext4/page-io.c:186 [inline]
 ext4_do_flush_completed_IO fs/ext4/page-io.c:259 [inline]
 ext4_end_io_rsv_work+0x368/0x6e0 fs/ext4/page-io.c:273
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

Crashes (26):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/03/18 12:36 linux-5.15.y b95c01af2113 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/03/17 21:31 linux-5.15.y b95c01af2113 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/03/16 12:04 linux-5.15.y b95c01af2113 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/03/14 11:21 linux-5.15.y 574362648507 8d8ee116 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/03/11 01:18 linux-5.15.y 574362648507 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/03/09 18:23 linux-5.15.y 574362648507 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/03/09 15:41 linux-5.15.y 574362648507 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/03/08 11:40 linux-5.15.y 574362648507 cf82cde1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in linkwatch_event
2024/03/07 04:47 linux-5.15.y 574362648507 f39a7eed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/03/05 07:23 linux-5.15.y 80efc6265290 5fc53669 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in linkwatch_event
2024/02/29 20:28 linux-5.15.y 458ce51d0356 352ab904 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in linkwatch_event
2024/02/27 09:23 linux-5.15.y 458ce51d0356 05e69c83 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/02/26 08:41 linux-5.15.y 458ce51d0356 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/02/24 06:09 linux-5.15.y 458ce51d0356 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/02/23 23:29 linux-5.15.y 458ce51d0356 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/02/18 19:09 linux-5.15.y 6139f2a02fe0 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/02/18 17:22 linux-5.15.y 6139f2a02fe0 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in linkwatch_event
2024/02/16 15:51 linux-5.15.y 6139f2a02fe0 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in linkwatch_event
2024/02/07 14:23 linux-5.15.y 6139f2a02fe0 6404acf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in linkwatch_event
2024/02/06 11:56 linux-5.15.y 6139f2a02fe0 6404acf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in linkwatch_event
2024/01/29 21:40 linux-5.15.y 6139f2a02fe0 991a98f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in linkwatch_event
2024/01/28 23:10 linux-5.15.y 6139f2a02fe0 cc4a4020 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/01/25 02:58 linux-5.15.y ddcaf4999061 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/01/24 23:18 linux-5.15.y ddcaf4999061 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/01/23 14:05 linux-5.15.y ddcaf4999061 1c0ecc51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
2024/01/11 11:31 linux-5.15.y 26c690eff0a5 00f3cc59 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf INFO: task hung in linkwatch_event
* Struck through repros no longer work on HEAD.