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: 133d, last: 11h38m
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 2d06h 825d 0/3 upstream: reported C repro on 2023/07/29 13:11
linux-6.1 INFO: task hung in read_part_sector 1 1 632d 632d 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 648d 714d 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 510d 510d 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 6d13h 95d 0/3 upstream: reported on 2025/07/28 11:29
upstream INFO: task hung in read_part_sector (2) block 1 4822 47m 453d 0/29 upstream: reported on 2024/08/04 19:22

Sample crash report:
INFO: task udevd:5799 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:22568 pid:5799  ppid:5160   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5380 [inline]
 __schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
 schedule+0xbd/0x170 kernel/sched/core.c:6773
 io_schedule+0x80/0xd0 kernel/sched/core.c:9022
 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: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+0x274b/0x3190 fs/namei.c:3797
 do_filp_open+0x1c5/0x3d0 fs/namei.c:3824
 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:0x7f95ca8a7407
RSP: 002b:00007ffc4ae070e0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f95cb093880 RCX: 00007f95ca8a7407
RDX: 00000000000a0800 RSI: 000055fee11fcdd0 RDI: ffffffffffffff9c
RBP: 000055fee11db910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000055fee11f8f10
R13: 000055fee11f3410 R14: 0000000000000000 R15: 000055fee11f8f10
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by getty/5550:
 #0: ffff88802cef40a0 (&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+0x425/0x1380 drivers/tty/n_tty.c:2217
1 lock held by udevd/5799:
 #0: ffff8880217554c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x121/0x600 block/bdev.c:805
5 locks held by kworker/1:2/27856:
 #0: ffff8880b8f3c218 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:558
 #1: ffff8880b8f289c0 (psi_seq){-.-.}-{0:0}, at: psi_sched_switch kernel/sched/stats.h:189 [inline]
 #1: ffff8880b8f289c0 (psi_seq){-.-.}-{0:0}, at: __schedule+0x20ee/0x44d0 kernel/sched/core.c:6694
 #2: ffff88807d674ee0 (&r->consumer_lock#2){+.+.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]
 #2: ffff88807d674ee0 (&r->consumer_lock#2){+.+.}-{2:2}, at: ptr_ring_consume_bh include/linux/ptr_ring.h:365 [inline]
 #2: ffff88807d674ee0 (&r->consumer_lock#2){+.+.}-{2:2}, at: wg_packet_decrypt_worker+0x8e4/0xd90 drivers/net/wireguard/receive.c:499
 #3: ffff8880b8f3c218 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:558
 #4: ffff8880b8f289c0 (psi_seq){-.-.}-{0:0}, at: psi_enqueue kernel/sched/stats.h:143 [inline]
 #4: ffff8880b8f289c0 (psi_seq){-.-.}-{0:0}, at: enqueue_task+0x275/0x2c0 kernel/sched/core.c:2097

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

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/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: 1088 Comm: kworker/u4:6 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:85 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:102 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:127 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:159 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:178 [inline]
RIP: 0010:kasan_check_range+0x89/0x290 mm/kasan/generic.c:187
Code: 00 fc ff df 4d 8d 34 19 4d 89 f4 4d 29 dc 49 83 fc 10 7f 29 4d 85 e4 0f 84 41 01 00 00 4c 89 cb 48 f7 d3 4c 01 fb 41 80 3b 00 <0f> 85 cc 01 00 00 49 ff c3 48 ff c3 75 ee e9 21 01 00 00 44 89 dd
RSP: 0018:ffffc9000462f6c8 EFLAGS: 00000046
RAX: 0000000000000001 RBX: ffffffffffffffff RCX: ffffffff81670e5d
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff90da85d8
RBP: ffffc9000462f948 R08: ffffffff90da85df R09: 1ffffffff21b50bb
R10: dffffc0000000000 R11: fffffbfff21b50bb R12: 0000000000000001
R13: ffff8880237ebc00 R14: fffffbfff21b50bc R15: 1ffffffff21b50bb
FS:  0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005597b7b32168 CR3: 000000000cb30000 CR4: 00000000003506e0
DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000083
DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 instrument_atomic_read include/linux/instrumented.h:68 [inline]
 _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
 hlock_class kernel/locking/lockdep.c:228 [inline]
 __lock_acquire+0x107d/0x7c80 kernel/locking/lockdep.c:5133
 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
 _raw_spin_lock_bh+0x36/0x50 kernel/locking/spinlock.c:178
 spin_lock_bh include/linux/spinlock.h:356 [inline]
 batadv_nc_purge_paths+0xe7/0x3a0 net/batman-adv/network-coding.c:442
 batadv_nc_worker+0x328/0x610 net/batman-adv/network-coding.c:720
 process_one_work kernel/workqueue.c:2634 [inline]
 process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
 worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
 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>

Crashes (133):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/31 10:37 linux-6.6.y e5bbb12db2c7 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/30 02:35 linux-6.6.y e5bbb12db2c7 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/28 19:43 linux-6.6.y 4a243110dc88 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/25 02:25 linux-6.6.y 4a243110dc88 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/23 08:54 linux-6.6.y f231f248323d c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/22 15:19 linux-6.6.y f231f248323d 252fbbad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/21 19:39 linux-6.6.y f231f248323d 9832ed61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/18 12:48 linux-6.6.y 0bbbd97a442d 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/18 12:39 linux-6.6.y 0bbbd97a442d 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/18 07:09 linux-6.6.y 0bbbd97a442d 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/18 06:00 linux-6.6.y 0bbbd97a442d 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/18 04:42 linux-6.6.y 0bbbd97a442d 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/17 16:53 linux-6.6.y 0bbbd97a442d 7adf5298 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/16 21:41 linux-6.6.y 0bbbd97a442d 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/16 00:00 linux-6.6.y 0bbbd97a442d 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/13 18:13 linux-6.6.y 655054d2c3c1 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/12 19:17 linux-6.6.y 655054d2c3c1 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/12 18:16 linux-6.6.y 655054d2c3c1 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/12 08:12 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/11 21:20 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/11 16:27 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/11 13:38 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/11 13:18 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/11 07:03 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/11 05:39 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/10 12:50 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/10 12:41 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/06 21:20 linux-6.6.y e617101e5626 91305dbe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/05 07:53 linux-6.6.y f34f16e5c632 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/10/02 10:36 linux-6.6.y 147338df3487 267f56c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/29 09:42 linux-6.6.y 147338df3487 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/28 18:56 linux-6.6.y 147338df3487 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/26 16:06 linux-6.6.y 147338df3487 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/25 05:02 linux-6.6.y af1544b5d072 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/23 15:03 linux-6.6.y af1544b5d072 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/20 07:49 linux-6.6.y af1544b5d072 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/12 22:35 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/12 07:46 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/10 12:29 linux-6.6.y fe9731e10004 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/08 12:35 linux-6.6.y 355bd0b51d2f d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/08 12:33 linux-6.6.y 355bd0b51d2f d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/06 23:00 linux-6.6.y 355bd0b51d2f d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/06 22:49 linux-6.6.y 355bd0b51d2f d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2025/09/06 21:42 linux-6.6.y 355bd0b51d2f d291dd2d .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.