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: 17d, last: 1d16h
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in read_part_sector origin:upstream C error 132 3d05h 708d 0/3 upstream: reported C repro on 2023/07/29 13:11
linux-6.1 INFO: task hung in read_part_sector 1 516d 516d 0/3 auto-obsoleted due to no activity on 2024/05/17 07:34
upstream INFO: task hung in read_part_sector block 2 532d 598d 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 394d 394d 0/3 auto-obsoleted due to no activity on 2024/09/16 08:59
upstream INFO: task hung in read_part_sector (2) block 675 45m 336d 0/29 upstream: reported on 2024/08/04 19:22

Sample crash report:
INFO: task udevd:18221 blocked for more than 144 seconds.
      Not tainted 6.6.95-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd           state:D stack:23688 pid:18221 ppid:5159   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x14e2/0x4580 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+0x6eb/0xf70 mm/filemap.c:1329
 folio_put_wait_locked mm/filemap.c:1493 [inline]
 do_read_cache_folio+0x1c0/0x7e0 mm/filemap.c:3771
 read_mapping_folio include/linux/pagemap.h:898 [inline]
 read_part_sector+0xd2/0x350 block/partitions/core.c:718
 adfspart_check_POWERTEC+0x8d/0xf00 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+0x73a/0x1410 block/partitions/core.c:689
 blkdev_get_whole+0x30d/0x390 block/bdev.c:655
 blkdev_get_by_dev+0x279/0x600 block/bdev.c:797
 blkdev_open+0x152/0x360 block/fops.c:589
 do_dentry_open+0x8c6/0x1500 fs/open.c:929
 do_open fs/namei.c:3632 [inline]
 path_openat+0x274b/0x3190 fs/namei.c:3789
 do_filp_open+0x1c5/0x3d0 fs/namei.c:3816
 do_sys_openat2+0x12c/0x1c0 fs/open.c:1419
 do_sys_open fs/open.c:1434 [inline]
 __do_sys_openat fs/open.c:1450 [inline]
 __se_sys_openat fs/open.c:1445 [inline]
 __x64_sys_openat+0x139/0x160 fs/open.c:1445
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff3502a7407
RSP: 002b:00007ffc2c2152d0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007ff350956880 RCX: 00007ff3502a7407
RDX: 00000000000a0800 RSI: 00005593d27bf370 RDI: ffffffffffffff9c
RBP: 00005593d27be910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00005593d27dbf20
R13: 00005593d27d6420 R14: 0000000000000000 R15: 00005593d27dbf20
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8cd2f760 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
3 locks held by kworker/0:2/1187:
2 locks held by getty/5551:
 #0: ffff888031eb20a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
1 lock held by udevd/18221:
 #0: ffff8881413d84c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x121/0x600 block/bdev.c:788
1 lock held by udevd/19457:
 #0: ffff888021cc24c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x121/0x600 block/bdev.c:788
1 lock held by syz.4.4774/25826:
 #0: ffffffff8cd35600 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:4085
1 lock held by dhcpcd-run-hook/25829:
 #0: ffff8880b8e3c458 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:558

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

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x39b/0x3d0 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+0xf41/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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 25845 Comm: dhcpcd-run-hook Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:__asan_memset+0x5/0x40 mm/kasan/shadow.c:83
Code: 0f 1f 44 00 00 f3 0f 1e fa 89 f6 48 8b 0c 24 ba 01 00 00 00 e9 bc ea ff ff 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 55 <41> 56 53 48 89 d3 89 f5 49 89 fe 48 8b 4c 24 18 48 89 d6 ba 01 00
RSP: 0000:ffffc90005117490 EFLAGS: 00000246
RAX: ffffffff813ac13f RBX: ffffc90005117508 RCX: ffff88806d22bc00
RDX: 0000000000000060 RSI: 0000000000000000 RDI: ffffc90005117508
RBP: dffffc0000000000 R08: ffffc900051176ff R09: 0000000000000000
R10: ffffc90005117680 R11: fffff52000a22ee0 R12: 0000000000000000
R13: ffff88806d22bc00 R14: ffffffff81746190 R15: 0000000000000000
FS:  00007f42600b6c80(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b7f5b006c0 CR3: 000000006b77a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 000000000214000e DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __unwind_start+0x3e/0x7e0 arch/x86/kernel/unwind_orc.c:688
 unwind_start arch/x86/include/asm/unwind.h:64 [inline]
 arch_stack_walk+0xf8/0x190 arch/x86/kernel/stacktrace.c:24
 stack_trace_save+0x9c/0xe0 kernel/stacktrace.c:122
 save_stack+0xf7/0x1f0 mm/page_owner.c:128
 __set_page_owner+0x1d/0x60 mm/page_owner.c:192
 set_page_owner include/linux/page_owner.h:31 [inline]
 post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
 prep_new_page mm/page_alloc.c:1561 [inline]
 get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
 __alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
 __folio_alloc+0x10/0x20 mm/page_alloc.c:4489
 vma_alloc_folio+0x47a/0x8f0 mm/mempolicy.c:2242
 wp_page_copy mm/memory.c:3093 [inline]
 do_wp_page+0x12bd/0x3630 mm/memory.c:3468
 handle_pte_fault mm/memory.c:5041 [inline]
 __handle_mm_fault mm/memory.c:5166 [inline]
 handle_mm_fault+0x12d4/0x4920 mm/memory.c:5331
 do_user_addr_fault+0xad0/0x12e0 arch/x86/mm/fault.c:1324
 handle_page_fault arch/x86/mm/fault.c:1465 [inline]
 exc_page_fault+0x67/0x110 arch/x86/mm/fault.c:1521
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7f4260217b8e
Code: 48 8d 05 55 8f 13 00 48 39 c5 0f 95 c0 0f b6 c0 48 c1 e0 02 48 09 d8 48 83 c8 01 49 89 45 08 48 89 c8 48 83 c8 01 48 89 42 08 <4b> 89 4c 35 00 8b 05 c3 f6 13 00 49 8d 4d 10 85 c0 0f 84 29 fa ff
RSP: 002b:00007ffca516a6c0 EFLAGS: 00010202
RAX: 0000000000001501 RBX: 00000000000003c0 RCX: 0000000000001500
RDX: 000055b7f5aff1c0 RSI: 00007f4260351180 RDI: 000055b7f5afee00
RBP: 00007f4260350ac0 R08: 00007f4260350ac0 R09: 00000000000003c0
R10: 0000000000000003 R11: 0000000000000001 R12: 00000000000003b8
R13: 000055b7f5afee00 R14: 00000000000018c0 R15: 00007f4260350b20
 </TASK>

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/05 20:08 linux-6.6.y 3f5b4c104b7d 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/07/05 20:05 linux-6.6.y 3f5b4c104b7d 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/06/30 01:50 linux-6.6.y 3f5b4c104b7d fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/06/23 00:25 linux-6.6.y 6282921b6825 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/06/21 14:00 linux-6.6.y 6282921b6825 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/06/21 06:39 linux-6.6.y 6282921b6825 d6cdfb8a .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.