syzbot


INFO: task hung in read_part_sector (2)

Status: upstream: reported on 2024/08/04 19:22
Subsystems: block
[Documentation on labels]
Reported-by: syzbot+82de77d3f217960f087d@syzkaller.appspotmail.com
First crash: 527d, last: 44m
Discussions (8)
Title Replies (including bot) Last reply
[syzbot] Monthly block report (Sep 2025) 0 (1) 2025/09/27 20:43
[syzbot] Monthly block report (Aug 2025) 0 (1) 2025/08/27 08:15
[syzbot] Monthly block report (Jul 2025) 0 (1) 2025/07/27 10:41
[syzbot] Monthly block report (Jun 2025) 0 (1) 2025/06/26 05:36
[syzbot] Monthly block report (Apr 2025) 0 (1) 2025/04/24 13:06
[syzbot] Monthly block report (Mar 2025) 0 (1) 2025/03/24 18:56
[syzbot] Monthly block report (Oct 2024) 0 (1) 2024/10/16 15:35
[syzbot] [block?] INFO: task hung in read_part_sector (2) 0 (1) 2024/08/04 19:22
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in read_part_sector origin:upstream 1 C error 255 1d05h 824d 0/3 upstream: reported C repro on 2023/07/29 13:11
linux-6.1 INFO: task hung in read_part_sector 1 1 631d 631d 0/3 auto-obsoleted due to no activity on 2024/05/17 07:34
upstream INFO: task hung in read_part_sector block 1 2 647d 713d 0/29 auto-obsoleted due to no activity on 2024/04/21 10:47
linux-6.6 INFO: task hung in read_part_sector 1 132 18h21m 132d 0/2 upstream: reported on 2025/06/19 22:23
linux-6.1 INFO: task hung in read_part_sector (2) 1 1 509d 509d 0/3 auto-obsoleted due to no activity on 2024/09/16 08:59
linux-6.1 INFO: task hung in read_part_sector (3) 1 3 5d12h 94d 0/3 upstream: reported on 2025/07/28 11:29

Sample crash report:
INFO: task udevd:12899 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd           state:D stack:23880 pid:12899 tgid:12899 ppid:5182   task_flags:0x400140 flags:0x00080003
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5325 [inline]
 __schedule+0x1190/0x5de0 kernel/sched/core.c:6929
 __schedule_loop kernel/sched/core.c:7011 [inline]
 schedule+0xe7/0x3a0 kernel/sched/core.c:7026
 io_schedule+0xbf/0x130 kernel/sched/core.c:7871
 folio_wait_bit_common+0x3d5/0x9e0 mm/filemap.c:1330
 folio_put_wait_locked mm/filemap.c:1494 [inline]
 do_read_cache_folio+0x342/0x5c0 mm/filemap.c:4006
 read_mapping_folio include/linux/pagemap.h:999 [inline]
 read_part_sector+0xd4/0x370 block/partitions/core.c:722
 adfspart_check_POWERTEC+0x8a/0x710 block/partitions/acorn.c:454
 check_partition block/partitions/core.c:141 [inline]
 blk_add_partitions block/partitions/core.c:589 [inline]
 bdev_disk_changed+0x723/0x1520 block/partitions/core.c:693
 blkdev_get_whole+0x187/0x290 block/bdev.c:748
 bdev_open+0x2c7/0xe40 block/bdev.c:957
 blkdev_open+0x34e/0x4f0 block/fops.c:701
 do_dentry_open+0x982/0x1530 fs/open.c:965
 vfs_open+0x82/0x3f0 fs/open.c:1097
 do_open fs/namei.c:3975 [inline]
 path_openat+0x1de4/0x2cb0 fs/namei.c:4134
 do_filp_open+0x20b/0x470 fs/namei.c:4161
 do_sys_openat2+0x11b/0x1d0 fs/open.c:1437
 do_sys_open fs/open.c:1452 [inline]
 __do_sys_openat fs/open.c:1468 [inline]
 __se_sys_openat fs/open.c:1463 [inline]
 __x64_sys_openat+0x174/0x210 fs/open.c:1463
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f29e42a7407
RSP: 002b:00007ffe22420450 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f29e498f880 RCX: 00007f29e42a7407
RDX: 00000000000a0800 RSI: 000055adace18460 RDI: ffffffffffffff9c
RBP: 000055adace152c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000055adad057d50
R13: 000055adad0508d0 R14: 0000000000000000 R15: 000055adad057d50
 </TASK>

Showing all locks held in the system:
6 locks held by kworker/1:0/24:
 #0: ffff8880232c7148 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x12a2/0x1b70 kernel/workqueue.c:3238
 #1: ffffc900001e7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x929/0x1b70 kernel/workqueue.c:3239
 #2: ffff888029287198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:914 [inline]
 #2: ffff888029287198 (&dev->mutex){....}-{4:4}, at: hub_event+0x1c0/0x4fe0 drivers/usb/core/hub.c:5898
 #3: ffff888035244198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:914 [inline]
 #3: ffff888035244198 (&dev->mutex){....}-{4:4}, at: __device_attach+0x7e/0x4b0 drivers/base/dd.c:1006
 #4: ffff888078de2160 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:914 [inline]
 #4: ffff888078de2160 (&dev->mutex){....}-{4:4}, at: __device_attach+0x7e/0x4b0 drivers/base/dd.c:1006
 #5: ffffffff8e2771d0 (umhelper_sem){++++}-{4:4}, at: usermodehelper_read_trylock+0xa9/0x250 kernel/umh.c:214
1 lock held by khungtaskd/31:
 #0: ffffffff8e3c4460 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e3c4460 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #0: ffffffff8e3c4460 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x36/0x1c0 kernel/locking/lockdep.c:6775
2 locks held by getty/5569:
 #0: ffff888035b5d0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000332e2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x41b/0x14f0 drivers/tty/n_tty.c:2222
5 locks held by kworker/u8:10/6830:
1 lock held by udevd/12899:
 #0: ffff888143706358 (&disk->open_mutex){+.+.}-{4:4}, at: bdev_open+0x41a/0xe40 block/bdev.c:945
1 lock held by syz-executor/18840:
 #0: ffff8880b843a398 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:646 [inline]
 #0: ffff8880b843a398 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x7e/0x130 kernel/sched/core.c:631
1 lock held by syz.0.3654/19002:
 #0: ffff888143706358 (&disk->open_mutex){+.+.}-{4:4}, at: bdev_open+0x41a/0xe40 block/bdev.c:945

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x27b/0x390 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x29c/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:332 [inline]
 watchdog+0xf3f/0x1170 kernel/hung_task.c:495
 kthread+0x3c5/0x780 kernel/kthread.c:463
 ret_from_fork+0x675/0x7d0 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:pv_native_safe_halt+0xf/0x20 arch/x86/kernel/paravirt.c:82
Code: 07 6d 02 c3 cc cc cc cc 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 0f 00 2d 43 d5 29 00 fb f4 <e9> 3c 0a 03 00 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90
RSP: 0018:ffffc90000197de8 EFLAGS: 000002c6
RAX: 0000000002e7dd17 RBX: 0000000000000001 RCX: ffffffff8b6052a9
RDX: 0000000000000000 RSI: ffffffff8da2a287 RDI: ffffffff8bf06e40
RBP: ffffed1003adc490 R08: 0000000000000001 R09: ffffed10170a6655
R10: ffff8880b85332ab R11: 0000000000000001 R12: 0000000000000001
R13: ffff88801d6e2480 R14: ffffffff9081f6d0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff888124b0a000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1a0a7b3ad8 CR3: 0000000064c8c000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 arch_safe_halt arch/x86/include/asm/paravirt.h:107 [inline]
 default_idle+0x13/0x20 arch/x86/kernel/process.c:767
 default_idle_call+0x6c/0xb0 kernel/sched/idle.c:122
 cpuidle_idle_call kernel/sched/idle.c:190 [inline]
 do_idle+0x38d/0x500 kernel/sched/idle.c:330
 cpu_startup_entry+0x4f/0x60 kernel/sched/idle.c:428
 start_secondary+0x21d/0x2b0 arch/x86/kernel/smpboot.c:315
 common_startup_64+0x13e/0x148
 </TASK>

Crashes (4741):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/30 16:18 upstream e53642b87a4f fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in read_part_sector
2025/10/30 01:07 upstream e53642b87a4f fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in read_part_sector
2025/10/29 21:40 upstream e53642b87a4f fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2025/10/28 14:55 upstream fd57572253bc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2025/10/28 14:27 upstream fd57572253bc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in read_part_sector
2025/10/28 06:36 upstream fd57572253bc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2025/10/28 03:48 upstream dcb6fa37fd7b fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2025/10/27 17:59 upstream dcb6fa37fd7b fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in read_part_sector
2025/03/02 00:05 upstream 03d38806a902 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in read_part_sector
2024/07/31 19:09 upstream e4fc196f5ba3 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2024/07/24 08:02 upstream 28bbe4ea686a 57b2edb1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2025/10/30 20:12 net 51e5ad549c43 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/30 19:17 net 51e5ad549c43 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/30 10:35 net 00764aa5c9bb fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/30 09:07 net 00764aa5c9bb fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/30 05:37 net 00764aa5c9bb fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 23:06 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 20:03 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 18:32 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 17:22 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 16:22 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 14:06 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 12:22 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 09:57 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 07:43 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/29 04:42 net 8df206f7b636 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/28 21:59 net 210b35d6a7ea fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/28 19:56 net 210b35d6a7ea fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/28 17:35 net 210b35d6a7ea fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/28 12:33 net 65f9c4c58889 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/28 09:49 net 65f9c4c58889 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/28 07:44 net 65f9c4c58889 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/28 05:25 net 65f9c4c58889 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/27 21:11 net 84a905290cb4 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/27 19:50 net 84a905290cb4 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/10/30 17:53 net-next 7ea7694495db fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/30 11:46 net-next efd3e30e651d fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/30 07:26 net-next efd3e30e651d fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/30 04:31 net-next efd3e30e651d fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/30 02:38 net-next efd3e30e651d fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/29 21:42 net-next a8abe8e210c1 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/29 10:14 net-next a8abe8e210c1 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/29 06:35 net-next a8abe8e210c1 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/29 03:22 net-next a8abe8e210c1 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/29 01:44 net-next 968822086b74 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/28 02:01 net-next 5f30bc470672 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/28 00:54 net-next 5f30bc470672 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/10/29 00:42 linux-next f7d2388eeec2 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in read_part_sector
2025/10/29 00:41 linux-next f7d2388eeec2 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in read_part_sector
2025/10/28 10:55 linux-next f7d2388eeec2 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in read_part_sector
2025/10/27 23:35 linux-next 8fec172c82c2 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in read_part_sector
* Struck through repros no longer work on HEAD.