syzbot


INFO: task hung in uevent_show

Status: upstream: reported syz repro on 2024/08/12 05:03
Reported-by: syzbot+49ec46118b7484c7ab31@syzkaller.appspotmail.com
First crash: 343d, last: 7d16h
Bug presence (1)
Date Name Commit Repro Result
2024/12/22 upstream (ToT) bcde95ce32b6 C Didn't crash
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in uevent_show usb 1 C done 9704 342d 403d 28/29 fixed on 2024/10/22 11:56
android-6-12 INFO: task hung in uevent_show origin:upstream 1 syz 7 28d 31d 0/1 premoderation: reported syz repro on 2025/06/19 15:22
linux-6.1 INFO: task hung in uevent_show origin:lts-only 1 C 23 21d 360d 0/3 upstream: reported C repro on 2024/07/26 06:22
upstream INFO: task hung in uevent_show (2) kernel 1 C inconclusive 8325 15d 253d 29/29 fixed on 2025/07/17 21:22

Sample crash report:
INFO: task udevd:6392 blocked for more than 143 seconds.
      Not tainted 5.15.187-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd           state:D stack:25120 pid: 6392 ppid:  3561 flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x11b8/0x43b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1e0 kernel/sched/core.c:6459
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
 __mutex_lock_common+0xc71/0x2390 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 device_lock include/linux/device.h:760 [inline]
 uevent_show+0x17a/0x330 drivers/base/core.c:2408
 dev_attr_show+0x50/0xb0 drivers/base/core.c:2110
 sysfs_kf_seq_show+0x316/0x4c0 fs/sysfs/file.c:61
 seq_read_iter+0x49b/0xd50 fs/seq_file.c:230
 call_read_iter include/linux/fs.h:2166 [inline]
 new_sync_read fs/read_write.c:404 [inline]
 vfs_read+0x725/0xcf0 fs/read_write.c:485
 ksys_read+0x14d/0x250 fs/read_write.c:623
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f4a1a644407
RSP: 002b:00007ffd6ff46580 EFLAGS: 00000202 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007f4a1a556880 RCX: 00007f4a1a644407
RDX: 0000000000001000 RSI: 0000561868304950 RDI: 0000000000000008
RBP: 00007f4a1a78cff0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000000000000000a
R13: 00007f4a1a78cea0 R14: 0000000000000000 R15: 00005618682f9ca0
 </TASK>

Showing all locks held in the system:
5 locks held by kworker/0:1/13:
1 lock held by khungtaskd/27:
 #0: ffffffff8c11c2e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
4 locks held by kworker/u4:1/142:
3 locks held by kworker/u4:4/1327:
2 locks held by getty/3945:
 #0: ffff88807f551098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900025e62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
1 lock held by syz-executor/5442:
2 locks held by kworker/0:28/6078:
 #0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc900038ffd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
6 locks held by kworker/0:29/6079:
 #0: ffff8881423bed38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc90003d1fd00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffff88814819c220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #2: ffff88814819c220 (&dev->mutex){....}-{3:3}, at: hub_event+0x18f/0x4fa0 drivers/usb/core/hub.c:5781
 #3: ffff888065615220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #3: ffff888065615220 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x460 drivers/base/dd.c:954
 #4: ffff888022f951a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #4: ffff888022f951a8 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x460 drivers/base/dd.c:954
 #5: ffffffff8bfccb70 (umhelper_sem){++++}-{3:3}, at: usermodehelper_read_trylock+0xe7/0x320 kernel/umh.c:217
6 locks held by kworker/0:31/6081:
 #0: ffff8881423bed38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc90003d3fd00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffff88814812d220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #2: ffff88814812d220 (&dev->mutex){....}-{3:3}, at: hub_event+0x18f/0x4fa0 drivers/usb/core/hub.c:5781
 #3: ffff88801efcd220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #3: ffff88801efcd220 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x460 drivers/base/dd.c:954
 #4: ffff8880236a71a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #4: ffff8880236a71a8 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x460 drivers/base/dd.c:954
 #5: ffffffff8d1e02e8 (register_mutex#6){+.+.}-{3:3}, at: usb_audio_probe+0x38a/0x1d50 sound/usb/card.c:806
4 locks held by udevd/6392:
 #0: ffff88805b276790 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xad/0xd50 fs/seq_file.c:182
 #1: ffff88805f114088 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x51/0x3c0 fs/kernfs/file.c:112
 #2: ffff8881480642c0 (kn->active#32){++++}-{0:0}, at: kernfs_seq_start+0x71/0x3c0 fs/kernfs/file.c:113
 #3: ffff88814819c220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #3: ffff88814819c220 (&dev->mutex){....}-{3:3}, at: uevent_show+0x17a/0x330 drivers/base/core.c:2408
4 locks held by syz-executor/6662:
 #0: ffff888079764ff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5f/0x1030 net/bluetooth/hci_core.c:1737
 #1: ffff888079764078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x3f4/0x1030 net/bluetooth/hci_core.c:1782
 #2: ffffffff8d37d968 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1517 [inline]
 #2: ffffffff8d37d968 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xa4/0x220 net/bluetooth/hci_conn.c:1622
 #3: ffffffff8c120d68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
 #3: ffffffff8c120d68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
1 lock held by syz.5.972/10081:
 #0: ffff88814819c220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #0: ffff88814819c220 (&dev->mutex){....}-{3:3}, at: usbdev_open+0x16b/0x790 drivers/usb/core/devio.c:1040
1 lock held by syz.9.1099/10955:
 #0: ffff8881476f3468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xaa/0xb90 drivers/block/loop.c:1366
1 lock held by dhcpcd/10997:
 #0: ffff88806ff3ac10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #0: ffff88806ff3ac10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff88806ff3ac10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1336
1 lock held by dhcpcd/10998:
 #0: ffff8880595f4120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1694 [inline]
 #0: ffff8880595f4120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x35/0xce0 net/packet/af_packet.c:3213
1 lock held by dhcpcd/10999:
 #0: ffff8880609ec120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1694 [inline]
 #0: ffff8880609ec120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x35/0xce0 net/packet/af_packet.c:3213
2 locks held by dhcpcd/11000:
 #0: ffff88807551a120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1694 [inline]
 #0: ffff88807551a120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x35/0xce0 net/packet/af_packet.c:3213
 #1: ffffffff8c120d68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
 #1: ffffffff8c120d68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.187-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xe0f/0xe50 kernel/hung_task.c:369
 kthread+0x436/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 11018 Comm: dhcpcd-run-hook Not tainted 5.15.187-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:memset_erms+0x9/0x10 arch/x86/lib/memset_64.S:64
Code: c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 <f3> aa 4c 89 c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01 01
RSP: 0018:ffffc900049e7918 EFLAGS: 00010246
RAX: ffff88801e744f00 RBX: 0000000000000000 RCX: 0000000000000100
RDX: 0000000000000340 RSI: 0000000000000000 RDI: ffff88801e745140
RBP: 0000000000000001 R08: ffffffff89c000ca R09: ffff88801e744f00
R10: 0000000022332f96 R11: 000000007833c9e5 R12: 0000000000000001
R13: ffff888140007780 R14: 0000000000000cc0 R15: ffffc900049e7988
FS:  00007f95eb8b4c80(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b9c0c2b048 CR3: 000000005619c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 slab_post_alloc_hook+0x68/0x380 mm/slab.h:521
 slab_alloc_node mm/slub.c:3220 [inline]
 slab_alloc mm/slub.c:3228 [inline]
 kmem_cache_alloc+0x100/0x290 mm/slub.c:3233
 dup_fd+0x51/0xcf0 fs/file.c:307
 copy_files+0x72/0xe0 kernel/fork.c:1564
 copy_process+0x1680/0x3e00 kernel/fork.c:2278
 kernel_clone+0x219/0x930 kernel/fork.c:2679
 __do_sys_clone kernel/fork.c:2796 [inline]
 __se_sys_clone kernel/fork.c:2780 [inline]
 __x64_sys_clone+0x170/0x1c0 kernel/fork.c:2780
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f95eba4e636
Code: 89 df e8 6d e8 f6 ff 45 31 c0 31 d2 31 f6 64 48 8b 04 25 10 00 00 00 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 52 89 c5 85 c0 75 31 64 48 8b 04 25 10 00 00
RSP: 002b:00007ffcaa37e170 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007ffcaa37e178 RCX: 00007f95eba4e636
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 000055b9c0c29c30 R08: 0000000000000000 R09: 0000000000000000
R10: 00007f95eb8b4f50 R11: 0000000000000246 R12: 000055b9c0c37358
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Crashes (35):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/13 18:14 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/07/13 07:36 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/07/13 04:14 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/07/12 18:24 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/06/27 23:44 linux-5.15.y 3dea0e7f549e fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/06/27 12:58 linux-5.15.y 3dea0e7f549e 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/05/27 11:03 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/05/18 04:11 linux-5.15.y 3b8db0e4f263 f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/05/17 22:37 linux-5.15.y 3b8db0e4f263 f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/05/13 09:30 linux-5.15.y 3b8db0e4f263 f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/05/08 06:42 linux-5.15.y 16fdf2c7111b dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/04/17 02:35 linux-5.15.y f7347f400572 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/04/14 20:50 linux-5.15.y f7347f400572 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/04/14 01:28 linux-5.15.y f7347f400572 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/03/17 03:03 linux-5.15.y 0c935c049b5c e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/02/25 16:06 linux-5.15.y c16c81c81336 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/02/24 13:37 linux-5.15.y c16c81c81336 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/02/23 14:41 linux-5.15.y c16c81c81336 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/02/23 08:28 linux-5.15.y c16c81c81336 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/02/18 23:03 linux-5.15.y c16c81c81336 9a14138f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/02/17 02:46 linux-5.15.y c16c81c81336 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/02/15 00:33 linux-5.15.y c16c81c81336 1022af74 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/01/13 22:12 linux-5.15.y 4735586da88e 249ceea9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/01/04 19:41 linux-5.15.y 91786f140358 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/01/04 19:40 linux-5.15.y 91786f140358 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/12/28 08:24 linux-5.15.y 91786f140358 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/12/22 07:36 linux-5.15.y 91786f140358 d7f584ee .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/12/02 11:08 linux-5.15.y 0a51d2d4527b 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/12/02 02:18 linux-5.15.y 0a51d2d4527b 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/12/01 22:58 linux-5.15.y 0a51d2d4527b 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/11/25 16:29 linux-5.15.y 0a51d2d4527b 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/11/20 18:41 linux-5.15.y 0a51d2d4527b 4fca1650 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/11/15 14:15 linux-5.15.y d98fd109f827 f6ede3a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2024/08/12 05:02 linux-5.15.y 7e89efd3ae1c 6f4edef4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in uevent_show
2025/05/03 12:00 linux-5.15.y 16fdf2c7111b b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in uevent_show
* Struck through repros no longer work on HEAD.