INFO: task hung in mmc_stop_host

Status: upstream: reported on 2026/09/05 04:28
Reported-by: syzbot+54c875491fbcfa7e2830@syzkaller.appspotmail.com
First crash: 1h13m, last: 1h13m
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in mmc_stop_host prio:high mmc 1 296 39m 11d 0/29 upstream: reported on 2026/08/25 00:03
linux-6.1 INFO: task hung in mmc_stop_host 1 2 24m 5d10h 0/3 upstream: reported on 2026/08/30 19:05
linux-6.6 INFO: task hung in mmc_stop_host 1 3 8h37m 21d 0/2 upstream: reported on 2026/08/14 22:00

Sample crash report:
INFO: task kworker/0:2:1110 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:2     state:D stack:25424 pid: 1110 ppid:     2 flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11c3/0x4350 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2093
 do_wait_for_common+0x295/0x460 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
 __flush_work+0x15a/0x210 kernel/workqueue.c:3094
 __cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3181
 __mmc_stop_host drivers/mmc/core/core.c:2294 [inline]
 mmc_stop_host+0xd5/0x460 drivers/mmc/core/core.c:2299
 mmc_remove_host+0x11/0x60 drivers/mmc/core/host.c:642
 vub300_disconnect+0x14b/0x2e0 drivers/mmc/host/vub300.c:2388
 usb_unbind_interface+0x203/0x870 drivers/usb/core/driver.c:458
 __device_release_driver drivers/base/dd.c:1249 [inline]
 device_release_driver_internal+0x487/0x710 drivers/base/dd.c:1282
 bus_remove_device+0x2dd/0x400 drivers/base/bus.c:531
 device_del+0x63f/0xa80 drivers/base/core.c:3615
 usb_disable_device+0x3e7/0x8a0 drivers/usb/core/message.c:1472
 usb_disconnect+0x33c/0x8a0 drivers/usb/core/hub.c:2292
 hub_port_connect drivers/usb/core/hub.c:5346 [inline]
 hub_port_connect_change drivers/usb/core/hub.c:5642 [inline]
 port_event drivers/usb/core/hub.c:5804 [inline]
 hub_event+0x1d64/0x5260 drivers/usb/core/hub.c:5886
 process_one_work+0x867/0xff0 kernel/workqueue.c:2310
 worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
INFO: task kworker/1:8:4295 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:8     state:D stack:25184 pid: 4295 ppid:     2 flags:0x00004000
Workqueue: events_freezable mmc_rescan
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11c3/0x4350 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2093
 do_wait_for_common+0x295/0x460 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
 mmc_wait_for_req_done+0x33/0x460 drivers/mmc/core/core.c:403
 mmc_wait_for_cmd+0x174/0x280 drivers/mmc/core/core.c:639
 mmc_go_idle+0x123/0x260 drivers/mmc/core/mmc_ops.c:162
 mmc_rescan_try_freq drivers/mmc/core/core.c:2075 [inline]
 mmc_rescan+0x672/0xe30 drivers/mmc/core/core.c:2256
 process_one_work+0x867/0xff0 kernel/workqueue.c:2310
 worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/0:2/1110:
 #0: ffff88801bc9e938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc900047b7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffff8881482ea220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:809 [inline]
 #2: ffff8881482ea220 (&dev->mutex){....}-{3:3}, at: hub_event+0x178/0x5260 drivers/usb/core/hub.c:5832
 #3: ffff888074bc8220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:809 [inline]
 #3: ffff888074bc8220 (&dev->mutex){....}-{3:3}, at: usb_disconnect+0xf8/0x8a0 drivers/usb/core/hub.c:2283
 #4: ffff8880774171a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:809 [inline]
 #4: ffff8880774171a8 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1064 [inline]
 #4: ffff8880774171a8 (&dev->mutex){....}-{3:3}, at: device_release_driver_internal+0xa1/0x710 drivers/base/dd.c:1279
1 lock held by dhcpcd/3851:
 #0: ffffffff8d44d008 (rtnl_mutex){+.+.}-{3:3}, at: devinet_ioctl+0x256/0x1ba0 net/ipv4/devinet.c:1076
2 locks held by getty/3948:
 #0: ffff88814cc58098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
2 locks held by syz-executor/4198:
 #0: ffff88802026b518 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf1/0x780 block/bdev.c:911
 #1: ffff8880202fd468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xb50 drivers/block/loop.c:1366
3 locks held by kworker/1:7/4244:
 #0: ffff888016c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000317fd00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffff88802b164240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x283/0x3380 drivers/net/netdevsim/fib.c:1480
2 locks held by udevd/4282:
 #0: ffff888020276d18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf1/0x780 block/bdev.c:911
 #1: ffff888020353468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xb50 drivers/block/loop.c:1366
2 locks held by kworker/1:8/4295:
 #0: ffff888016c71538 ((wq_completion)events_freezable){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc900038afd00 ((work_completion)(&(&host->detect)->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
2 locks held by kworker/1:17/5228:
 #0: ffff888016c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000407fd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
2 locks held by kworker/u4:12/5871:
4 locks held by kworker/u4:13/6004:
 #0: ffff888016dcd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000304fd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffffffff8d4410d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:589
 #3: ffffffff8d44d008 (rtnl_mutex){+.+.}-{3:3}, at: cleanup_net+0x60b/0xba0 net/core/net_namespace.c:625
3 locks held by kworker/u4:14/7528:
 #0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc900034efd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffffffff8d44d008 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
2 locks held by syz-executor/8016:
 #0: ffffffff8d44d008 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8d44d008 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x79f/0xf10 net/core/rtnetlink.c:5695
 #1: ffffffff8c3239e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
 #1: ffffffff8c3239e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2d1/0x750 kernel/rcu/tree_exp.h:845
2 locks held by syz.9.737/8045:

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3a2/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+0xe1b/0xe60 kernel/hung_task.c:369
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 0 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 0 skipped: idling at default_idle+0xb/0x10 arch/x86/kernel/process.c:729

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/05 04:27 linux-5.15.y 0996e0926f6b 4f7b22a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in mmc_stop_host
* Struck through repros no longer work on HEAD.