syzbot


INFO: task hung in read_part_sector

Status: upstream: reported on 2025/06/19 22:23
Reported-by: syzbot+df988a9b3a05646bca4c@syzkaller.appspotmail.com
First crash: 305d, last: 18h29m
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 436 1d02h 996d 0/3 upstream: reported C repro on 2023/07/29 13:11
linux-6.1 INFO: task hung in read_part_sector 1 1 803d 803d 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 819d 885d 0/29 auto-obsoleted due to no activity on 2024/04/21 10:47
linux-6.1 INFO: task hung in read_part_sector (2) 1 1 681d 681d 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 25 9h27m 266d 0/3 upstream: reported on 2025/07/28 11:29
upstream INFO: task hung in read_part_sector (2) block 1 syz error 53441 10m 624d 0/29 upstream: reported syz repro on 2024/08/04 19:22

Sample crash report:
INFO: task udevd:7496 blocked for more than 146 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd           state:D stack:24080 pid:7496  ppid:5137   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1553/0x45a0 kernel/sched/core.c:6700
 schedule+0xbd/0x170 kernel/sched/core.c:6774
 io_schedule+0x80/0xd0 kernel/sched/core.c:9023
 folio_wait_bit_common+0x714/0xfa0 mm/filemap.c:1329
 folio_put_wait_locked mm/filemap.c:1493 [inline]
 do_read_cache_folio+0x1c0/0x7d0 mm/filemap.c:3791
 read_mapping_folio include/linux/pagemap.h:898 [inline]
 read_part_sector+0xd2/0x340 block/partitions/core.c:718
 adfspart_check_POWERTEC+0x93/0xed0 block/partitions/acorn.c:454
 check_partition block/partitions/core.c:138 [inline]
 blk_add_partitions block/partitions/core.c:600 [inline]
 bdev_disk_changed+0x740/0x1420 block/partitions/core.c:689
 blkdev_get_whole+0x30d/0x390 block/bdev.c:672
 blkdev_get_by_dev+0x279/0x600 block/bdev.c:814
 blkdev_open+0x152/0x360 block/fops.c:589
 do_dentry_open+0x8c6/0x1500 fs/open.c:929
 do_open fs/namei.c:3640 [inline]
 path_openat+0x27f1/0x3230 fs/namei.c:3797
 do_filp_open+0x1f5/0x430 fs/namei.c:3824
 do_sys_openat2+0x134/0x1d0 fs/open.c:1421
 do_sys_open fs/open.c:1436 [inline]
 __do_sys_openat fs/open.c:1452 [inline]
 __se_sys_openat fs/open.c:1447 [inline]
 __x64_sys_openat+0x139/0x160 fs/open.c:1447
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f609d8a7407
RSP: 002b:00007ffe908643b0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f609df72880 RCX: 00007f609d8a7407
RDX: 00000000000a0800 RSI: 0000564865e01900 RDI: ffffffffffffff9c
RBP: 0000564865df0910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000564865e03e20
R13: 0000564865e08410 R14: 0000000000000000 R15: 0000564865e03e20
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by udevd/5137:
 #0: ffff8880b8e3c018 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0xa9/0x140 kernel/sched/core.c:567
 #1: ffff8880b8e289c0 (psi_seq){-.-.}-{0:0}, at: psi_sched_switch kernel/sched/stats.h:189 [inline]
 #1: ffff8880b8e289c0 (psi_seq){-.-.}-{0:0}, at: __schedule+0x2176/0x45a0 kernel/sched/core.c:6695
2 locks held by getty/5529:
 #0: ffff88814c8220a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000328b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x433/0x1390 drivers/tty/n_tty.c:2217
5 locks held by kworker/0:4/5807:
 #0: ffff8880b8e3c018 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0xa9/0x140 kernel/sched/core.c:567
 #1: ffff8880b8e289c0 (psi_seq){-.-.}-{0:0}, at: psi_sched_switch kernel/sched/stats.h:189 [inline]
 #1: ffff8880b8e289c0 (psi_seq){-.-.}-{0:0}, at: __schedule+0x2176/0x45a0 kernel/sched/core.c:6695
 #2: ffff8880b8e37898 (&ACCESS_PRIVATE(sdp, lock)){....}-{2:2}, at: spin_lock_irq include/linux/spinlock.h:376 [inline]
 #2: ffff8880b8e37898 (&ACCESS_PRIVATE(sdp, lock)){....}-{2:2}, at: srcu_invoke_callbacks+0x31e/0x460 kernel/rcu/srcutree.c:1749
 #3: ffff8880272d2818 (&p->pi_lock){-.-.}-{2:2}, at: class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:522 [inline]
 #3: ffff8880272d2818 (&p->pi_lock){-.-.}-{2:2}, at: try_to_wake_up+0x60/0x1190 kernel/sched/core.c:4233
 #4: ffff8880b8e3c018 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0xa9/0x140 kernel/sched/core.c:567
2 locks held by kworker/u4:19/6893:
1 lock held by udevd/7496:
 #0: ffff88802549e4c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x121/0x600 block/bdev.c:805
1 lock held by syz.1.2669/19106:
1 lock held by syz.4.2690/19193:
 #0: ffffffff8d137980 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:4089
1 lock held by syz.0.2689/19199:
 #0: ffffffff8d137980 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:4089
1 lock held by syz.5.2692/19203:
 #0: ffffffff8d137980 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:4089

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xf3d/0xf80 kernel/hung_task.c:379
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 0 Comm: swapper/0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
RIP: 0010:pv_native_safe_halt+0xf/0x10 arch/x86/kernel/paravirt.c:148
Code: 39 21 02 c3 cc cc cc cc cc cc cc f3 0f 1e fa 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 66 90 0f 00 2d e3 f3 41 00 fb f4 <c3> 66 0f 1f 00 55 41 57 41 56 41 54 53 50 8b 2f eb 2e 41 89 de 80
RSP: 0018:ffffffff8ce07d80 EFLAGS: 000002c6
RAX: ce89d97de2cccf00 RBX: ffffffff8162aa0d RCX: ce89d97de2cccf00
RDX: 0000000000000001 RSI: ffffffff8acac9e0 RDI: ffffffff8b1c8e60
RBP: ffffffff8ce07eb8 R08: ffff8880b8e36b2b R09: 1ffff110171c6d65
R10: dffffc0000000000 R11: ffffed10171c6d66 R12: 1ffffffff19c0fbc
R13: dffffc0000000000 R14: 1ffffffff19d2688 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fba97a4edd5 CR3: 000000002ec7b000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 arch_safe_halt arch/x86/include/asm/paravirt.h:108 [inline]
 default_idle+0x13/0x20 arch/x86/kernel/process.c:753
 default_idle_call+0x6c/0xa0 kernel/sched/idle.c:97
 cpuidle_idle_call kernel/sched/idle.c:178 [inline]
 do_idle+0x33d/0x590 kernel/sched/idle.c:302
 cpu_startup_entry+0x43/0x60 kernel/sched/idle.c:401
 rest_init+0x2e2/0x300 init/main.c:744
 arch_call_rest_init+0xe/0x10 init/main.c:841
 start_kernel+0x459/0x4e0 init/main.c:1086
 x86_64_start_reservations+0x2a/0x30 arch/x86/kernel/head64.c:555
 x86_64_start_kernel+0x60/0x60 arch/x86/kernel/head64.c:536
 secondary_startup_64_no_verify+0x179/0x17b
 </TASK>

Crashes (500):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/20 07:59 linux-6.6.y 9760bf04666d 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/18 09:25 linux-6.6.y 8cee53b8eaeb 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/17 08:51 linux-6.6.y 8cee53b8eaeb de0a551d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/15 13:58 linux-6.6.y 8cee53b8eaeb c441f497 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/15 09:27 linux-6.6.y 8cee53b8eaeb e2e976a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/13 04:59 linux-6.6.y 8cee53b8eaeb 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/12 19:57 linux-6.6.y 8cee53b8eaeb 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/09 14:21 linux-6.6.y 80de0a958133 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/08 08:24 linux-6.6.y 80de0a958133 2c961e87 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/07 00:44 linux-6.6.y 80de0a958133 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/05 05:07 linux-6.6.y c09fbcd31ae6 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/02 09:31 linux-6.6.y c09fbcd31ae6 0cb124d5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/02 07:17 linux-6.6.y c09fbcd31ae6 0cb124d5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/04/02 04:29 linux-6.6.y c09fbcd31ae6 0cb124d5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/31 19:43 linux-6.6.y c09fbcd31ae6 aeea1c72 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/29 00:56 linux-6.6.y c09fbcd31ae6 b5ceaad2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/27 22:41 linux-6.6.y c09fbcd31ae6 74a13a23 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/26 19:44 linux-6.6.y c09fbcd31ae6 766b6434 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/26 06:20 linux-6.6.y c09fbcd31ae6 c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/26 04:56 linux-6.6.y c09fbcd31ae6 c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/25 14:38 linux-6.6.y c09fbcd31ae6 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/25 05:44 linux-6.6.y 4fc00fe35d46 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/22 18:45 linux-6.6.y 4fc00fe35d46 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/21 18:57 linux-6.6.y 4fc00fe35d46 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/20 23:45 linux-6.6.y 4fc00fe35d46 ac6f1dff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/20 17:34 linux-6.6.y 4fc00fe35d46 ac6f1dff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/19 13:45 linux-6.6.y 4fc00fe35d46 bd6dcb30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/18 19:16 linux-6.6.y 4fc00fe35d46 0199f9a1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/18 13:23 linux-6.6.y 4fc00fe35d46 0199f9a1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/17 22:22 linux-6.6.y 4fc00fe35d46 c8810548 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/17 15:41 linux-6.6.y 4fc00fe35d46 c01bca74 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/12 02:53 linux-6.6.y 4fc00fe35d46 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/11 04:20 linux-6.6.y 4fc00fe35d46 86914af9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/10 21:58 linux-6.6.y 4fc00fe35d46 4683d576 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/07 20:56 linux-6.6.y 4fc00fe35d46 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/06 13:34 linux-6.6.y 4fc00fe35d46 41d8037d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/03 02:32 linux-6.6.y 7a137e9bfa0e 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/03/02 19:56 linux-6.6.y 7a137e9bfa0e b9dd6534 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/28 21:27 linux-6.6.y 7a137e9bfa0e 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/27 17:03 linux-6.6.y 7a137e9bfa0e 2cf092b8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/22 18:00 linux-6.6.y 7a137e9bfa0e 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/22 12:00 linux-6.6.y 7a137e9bfa0e 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/21 09:44 linux-6.6.y 7a137e9bfa0e 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/20 02:14 linux-6.6.y 7a137e9bfa0e c8d8c52d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/19 19:44 linux-6.6.y 7a137e9bfa0e c8d8c52d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/19 05:15 linux-6.6.y 56865d9b7074 746545b8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/18 05:11 linux-6.6.y 56865d9b7074 39751c21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/16 20:13 linux-6.6.y ae462074fde3 5d52cba5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/14 10:06 linux-6.6.y 1b4ef5214f17 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/13 21:27 linux-6.6.y 1b4ef5214f17 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/02/13 13:42 linux-6.6.y 1b4ef5214f17 6a673c50 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/06/19 22:23 linux-6.6.y 6282921b6825 ed3e87f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
* Struck through repros no longer work on HEAD.