syzbot


INFO: task hung in read_part_sector (3)

Status: upstream: reported on 2025/07/28 11:29
Reported-by: syzbot+910d3e8c08500bfcbc85@syzkaller.appspotmail.com
First crash: 200d, last: 6d12h
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 380 23h33m 930d 0/3 upstream: reported C repro on 2023/07/29 13:11
linux-6.1 INFO: task hung in read_part_sector 1 1 737d 737d 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 753d 819d 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 435 3h47m 238d 0/2 upstream: reported on 2025/06/19 22:23
linux-6.1 INFO: task hung in read_part_sector (2) 1 1 615d 615d 0/3 auto-obsoleted due to no activity on 2024/09/16 08:59
upstream INFO: task hung in read_part_sector (2) block 1 syz error 27365 now 557d 0/29 upstream: reported syz repro on 2024/08/04 19:22

Sample crash report:
INFO: task udevd:6953 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd           state:D stack:22928 pid:6953  ppid:3637   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5245 [inline]
 __schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
 schedule+0xb9/0x180 kernel/sched/core.c:6638
 io_schedule+0x7c/0xd0 kernel/sched/core.c:8798
 folio_wait_bit_common+0x70a/0xfa0 mm/filemap.c:1324
 folio_put_wait_locked mm/filemap.c:1493 [inline]
 do_read_cache_folio+0x1a9/0x760 mm/filemap.c:3641
 read_mapping_folio include/linux/pagemap.h:799 [inline]
 read_part_sector+0xce/0x350 block/partitions/core.c:724
 adfspart_check_POWERTEC+0xc0/0x890 block/partitions/acorn.c:454
 check_partition block/partitions/core.c:146 [inline]
 blk_add_partitions block/partitions/core.c:609 [inline]
 bdev_disk_changed+0x7d9/0x14a0 block/partitions/core.c:695
 blkdev_get_whole+0x2e8/0x370 block/bdev.c:704
 blkdev_get_by_dev+0x32e/0xa60 block/bdev.c:841
 blkdev_open+0x11e/0x2e0 block/fops.c:500
 do_dentry_open+0x7e9/0x10d0 fs/open.c:882
 do_open fs/namei.c:3634 [inline]
 path_openat+0x2635/0x2ee0 fs/namei.c:3791
 do_filp_open+0x1f1/0x430 fs/namei.c:3818
 do_sys_openat2+0x150/0x4b0 fs/open.c:1320
 do_sys_open fs/open.c:1336 [inline]
 __do_sys_openat fs/open.c:1352 [inline]
 __se_sys_openat fs/open.c:1347 [inline]
 __x64_sys_openat+0x135/0x160 fs/open.c:1347
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f645a0a7407
RSP: 002b:00007ffed86a5a90 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f645a7c3880 RCX: 00007f645a0a7407
RDX: 00000000000a0800 RSI: 000055afa02a3e90 RDI: ffffffffffffff9c
RBP: 000055afa0294910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000055afa02a8ba0
R13: 000055afa02ac410 R14: 0000000000000000 R15: 000055afa02a8ba0
 </TASK>

Showing all locks held in the system:
2 locks held by kworker/u4:1/11:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8cb2dfb0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8cb2e7d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
 #0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 #0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
 #0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
3 locks held by kworker/0:3/3653:
 #0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
 #1: ffffc90003337d00 (xfrm_state_gc_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
 #2: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
 #2: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2ec/0x890 kernel/rcu/tree_exp.h:962
2 locks held by getty/4024:
 #0: ffff88814d10b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x429/0x1390 drivers/tty/n_tty.c:2198
1 lock held by syz-executor/4268:
 #0: ffff8880b8f3ab18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:538
1 lock held by udevd/6953:
 #0: ffff8880254454c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x13d/0xa60 block/bdev.c:832
2 locks held by kworker/0:16/8768:
 #0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
 #1: ffffc90004fc7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
1 lock held by syz-executor/12299:
1 lock held by syz.3.2084/12650:
2 locks held by rm/12882:

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

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 01/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3e6/0x460 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
 watchdog+0xeee/0xf30 kernel/hung_task.c:377
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 12650 Comm: syz.3.2084 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
RIP: 0010:arch_irqs_disabled_flags arch/x86/include/asm/irqflags.h:125 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:132 [inline]
RIP: 0010:lock_acquire+0x1fb/0x4a0 kernel/locking/lockdep.c:5665
Code: 0f c1 05 58 39 9e 7e 83 f8 01 0f 85 03 01 00 00 43 c6 44 3d 04 00 48 c7 84 24 80 00 00 00 00 00 00 00 9c 8f 84 24 80 00 00 00 <f7> 84 24 80 00 00 00 00 02 00 00 43 c6 44 3d 04 f8 0f 85 f0 00 00
RSP: 0018:ffffc900039a6fe0 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 6569453f05c85500
RDX: 0000000000000000 RSI: ffffffff8a8c23a0 RDI: ffffffff8adf0d20
RBP: ffffc900039a70f8 R08: dffffc0000000000 R09: 1ffffffff215e848
R10: dffffc0000000000 R11: fffffbfff215e849 R12: 0000000000000000
R13: 1ffff92000734e08 R14: 0000000000000046 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000560bc77e3138 CR3: 000000000c88e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 rcu_read_lock include/linux/rcupdate.h:791 [inline]
 __mod_lruvec_page_state+0xbe/0x410 mm/memcontrol.c:832
 __lruvec_stat_mod_folio include/linux/vmstat.h:609 [inline]
 filemap_unaccount_folio+0x12a/0xa80 mm/filemap.c:183
 __filemap_remove_folio+0xbc/0x8a0 mm/filemap.c:222
 filemap_remove_folio+0xed/0x2c0 mm/filemap.c:255
 truncate_inode_folio+0x59/0x70 mm/truncate.c:195
 shmem_undo_range+0x533/0x20c0 mm/shmem.c:942
 shmem_truncate_range mm/shmem.c:1062 [inline]
 shmem_evict_inode+0x25b/0xa80 mm/shmem.c:1171
 evict+0x4c9/0x8d0 fs/inode.c:705
 __dentry_kill+0x431/0x650 fs/dcache.c:611
 dentry_kill+0xb8/0x290 fs/dcache.c:-1
 dput+0xfa/0x1d0 fs/dcache.c:918
 __fput+0x5e0/0x920 fs/file_table.c:328
 task_work_run+0x1d0/0x260 kernel/task_work.c:203
 exit_task_work include/linux/task_work.h:39 [inline]
 do_exit+0x982/0x2480 kernel/exit.c:880
 do_group_exit+0x217/0x2d0 kernel/exit.c:1022
 get_signal+0x1272/0x1350 kernel/signal.c:2871
 arch_do_signal_or_restart+0xc4/0x1350 arch/x86/kernel/signal.c:871
 exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
 irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:316
 exc_page_fault+0x88/0x100 arch/x86/mm/fault.c:1485
 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7f6f01b9aec1
Code: Unable to access opcode bytes at 0x7f6f01b9ae97.
RSP: 002b:0000000000000040 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f6f01e15fa0 RCX: 00007f6f01b9aeb9
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000081248080
RBP: 00007f6f01c08c1f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000
R13: 00007f6f01e16038 R14: 00007f6f01e15fa0 R15: 00007ffe688733f8
 </TASK>
vkms_vblank_simulate: vblank timer overrun

Crashes (19):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/02/07 05:05 linux-6.1.y 0182cb5b74ee f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2026/02/07 05:05 linux-6.1.y 0182cb5b74ee f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2026/01/26 11:57 linux-6.1.y cd9b81672742 a4c52dd6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2026/01/17 04:48 linux-6.1.y bec0e10ee67e 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2026/01/17 04:47 linux-6.1.y bec0e10ee67e 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2026/01/16 12:32 linux-6.1.y bec0e10ee67e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2026/01/15 22:39 linux-6.1.y bec0e10ee67e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2026/01/14 09:54 linux-6.1.y bec0e10ee67e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2026/01/13 16:23 linux-6.1.y bec0e10ee67e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/12/09 01:33 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/12/08 07:56 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/11/30 08:37 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/11/30 08:35 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/11/30 08:34 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/11/05 02:25 linux-6.1.y f6e38ae624cf 686bf657 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/11/04 09:11 linux-6.1.y f6e38ae624cf 686bf657 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/10/25 08:51 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/10/17 03:12 linux-6.1.y c2fda4b3f577 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
2025/07/28 11:29 linux-6.1.y 3594f306da12 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in read_part_sector
* Struck through repros no longer work on HEAD.