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: 400d, last: 10h22m
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 545 8h33m 1091d 0/3 upstream: reported C repro on 2023/07/29 13:11
linux-6.1 INFO: task hung in read_part_sector 1 1 898d 898d 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 914d 980d 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 776d 776d 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 36 25d 361d 0/3 upstream: reported on 2025/07/28 11:29
upstream INFO: task hung in read_part_sector (2) prio:low block 1 syz error error 68942 5m 719d 0/29 upstream: reported syz repro on 2024/08/04 19:22

Sample crash report:
INFO: task udevd:15721 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:23144 pid:15721 ppid:5137   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x15ae/0x4660 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+0x881/0xfa0 mm/filemap.c:1329
 folio_put_wait_locked mm/filemap.c:1493 [inline]
 do_read_cache_folio+0x1c0/0x7f0 mm/filemap.c:3791
 read_mapping_folio include/linux/pagemap.h:898 [inline]
 read_part_sector+0xd2/0x350 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+0x755/0x1450 block/partitions/core.c:689
 blkdev_get_whole+0x30d/0x390 block/bdev.c:672
 blkdev_get_by_dev+0x3a9/0x610 block/bdev.c:814
 blkdev_open+0x14e/0x360 block/fops.c:589
 do_dentry_open+0x880/0x14b0 fs/open.c:929
 do_open fs/namei.c:3640 [inline]
 path_openat+0x284f/0x3270 fs/namei.c:3797
 do_filp_open+0x1f2/0x430 fs/namei.c:3824
 do_sys_openat2+0x134/0x1d0 fs/open.c:1422
 do_sys_open fs/open.c:1437 [inline]
 __do_sys_openat fs/open.c:1453 [inline]
 __se_sys_openat fs/open.c:1448 [inline]
 __x64_sys_openat+0x139/0x160 fs/open.c:1448
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f4d496a7407
RSP: 002b:00007ffe1679fdc0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f4d49db4880 RCX: 00007f4d496a7407
RDX: 00000000000a0800 RSI: 00005568f3fcf8e0 RDI: ffffffffffffff9c
RBP: 00005568f3fa7910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00005568f3fc7f60
R13: 00005568f3fbf410 R14: 0000000000000000 R15: 00005568f3fc7f60
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by getty/5531:
 #0: ffff88803138a0a0 (&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+0x428/0x1370 drivers/tty/n_tty.c:2217
3 locks held by kworker/u4:16/7464:
 #0: ffff88802c3d3138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
 #0: ffff88802c3d3138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
 #1: ffffc900051a7d00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
 #1: ffffc900051a7d00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
 #2: ffffffff8e3d5b08 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xce/0x1550 net/ipv6/addrconf.c:4181
3 locks held by kworker/u4:22/7679:
 #0: ffff8880b8e3c298 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x29/0x130 kernel/sched/core.c:559
 #1: ffff8880b8e28a00 (psi_seq){-.-.}-{0:0}, at: psi_sched_switch kernel/sched/stats.h:189 [inline]
 #1: ffff8880b8e28a00 (psi_seq){-.-.}-{0:0}, at: __schedule+0x21d3/0x4660 kernel/sched/core.c:6695
 #2: ffff88805e698768 (&rdev->wiphy.mtx){+.+.}-{3:3}, at: wiphy_lock include/net/cfg80211.h:5777 [inline]
 #2: ffff88805e698768 (&rdev->wiphy.mtx){+.+.}-{3:3}, at: cfg80211_wiphy_work+0x35/0x260 net/wireless/core.c:424
3 locks held by kworker/1:7/15324:
 #0: ffff888017c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
 #0: ffff888017c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
 #1: ffffc9000447fd00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
 #1: ffffc9000447fd00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
 #2: ffff88802f619240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x285/0x32c0 drivers/net/netdevsim/fib.c:1491
1 lock held by udevd/15721:
 #0: ffff888141b884c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x11b/0x610 block/bdev.c:805
2 locks held by kworker/0:2/17146:
 #0: ffff888017c72538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
 #0: ffff888017c72538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
 #1: ffffc90003457d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
 #1: ffffc90003457d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
3 locks held by syz-executor/23220:
 #0: ffffffff8e3d5b08 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:78 [inline]
 #0: ffffffff8e3d5b08 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7ed/0xf90 net/core/rtnetlink.c:6473
 #1: ffff88801bab9468 (&wg->device_update_lock){+.+.}-{3:3}, at: wg_open+0x227/0x420 drivers/net/wireguard/device.c:50
 #2: ffffffff8d137778 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
 #2: ffffffff8d137778 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3da/0x880 kernel/rcu/tree_exp.h:1004
1 lock held by syz.2.4618/23409:
3 locks held by syz.8.4628/23467:
 #0: ffff88807821fa20 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
 #0: ffff88807821fa20 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:658 [inline]
 #0: ffff88807821fa20 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x82/0x210 net/socket.c:1421
 #1: ffff88802f330130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1780 [inline]
 #1: ffff88802f330130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_release+0x7f0/0xd60 net/packet/af_packet.c:3215
 #2: ffffffff8d137778 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
 #2: ffffffff8d137778 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3da/0x880 kernel/rcu/tree_exp.h:1004

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

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 07/16/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+0xf59/0xfa0 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: 23409 Comm: syz.2.4618 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:__local_bh_enable_ip+0x126/0x1c0 kernel/softirq.c:401
Code: d8 65 01 05 34 6c b1 7e 65 8b 05 2d 6c b1 7e a9 00 ff ff 00 75 19 48 c7 c7 80 c3 c9 8a e8 32 92 39 09 65 66 8b 05 2a 6c b1 7e <66> 85 c0 75 54 bf 01 00 00 00 e8 2b 1d 0a 00 e8 d6 06 3b 00 fb 65
RSP: 0018:ffffc900047876c0 EFLAGS: 00000082
RAX: 0000000000000000 RBX: 0000000000000201 RCX: 0701607ab4e9f300
RDX: dffffc0000000000 RSI: ffffffff8ac9c380 RDI: ffffffff8b1cfa20
RBP: ffffc90004787750 R08: ffffffff8e8c6b2f R09: 1ffffffff1d18d65
R10: dffffc0000000000 R11: fffffbfff1d18d66 R12: ffffffff89d0eee6
R13: dffffc0000000000 R14: dffffc0000000000 R15: 1ffff920008f0ed8
FS:  00007f84d343a6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000c99030 CR3: 000000005f0d0000 CR4: 00000000003506e0
Call Trace:
 <TASK>
 sctp_recvmsg+0x8e6/0xda0 net/sctp/socket.c:2207
 inet_recvmsg+0x140/0x1f0 net/ipv4/af_inet.c:882
 sock_recvmsg_nosec+0x82/0xd0 net/socket.c:1047
 ____sys_recvmsg+0x4d7/0x5d0 net/socket.c:2812
 ___sys_recvmsg+0x214/0x590 net/socket.c:2856
 do_recvmmsg+0x377/0x810 net/socket.c:2950
 __sys_recvmmsg net/socket.c:3029 [inline]
 __do_sys_recvmmsg net/socket.c:3052 [inline]
 __se_sys_recvmmsg net/socket.c:3045 [inline]
 __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3045
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f84d259de99
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f84d343a028 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: ffffffffffffffda RBX: 00007f84d2825fa0 RCX: 00007f84d259de99
RDX: 0000000004000169 RSI: 0000200000005000 RDI: 000000000000000a
RBP: 00007f84d2633eaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000060 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f84d2826038 R14: 00007f84d2825fa0 R15: 00007ffe7e2e66e8
 </TASK>

Crashes (619):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/07/24 11:58 linux-6.6.y da47cbc25466 544adce9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/18 02:32 linux-6.6.y da47cbc25466 8aaff637 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/17 23:42 linux-6.6.y da47cbc25466 8aaff637 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/09 19:54 linux-6.6.y da47cbc25466 a0c310a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/08 17:49 linux-6.6.y da47cbc25466 88a4b44c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/07 09:26 linux-6.6.y da47cbc25466 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/05 21:14 linux-6.6.y da47cbc25466 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/05 09:26 linux-6.6.y da47cbc25466 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/04 07:44 linux-6.6.y d1cfde2d5d15 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/01 12:51 linux-6.6.y d1cfde2d5d15 00a5cf1c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/07/01 12:47 linux-6.6.y d1cfde2d5d15 00a5cf1c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/30 22:48 linux-6.6.y d1cfde2d5d15 00e8b0fd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/30 10:35 linux-6.6.y d1cfde2d5d15 fff8d0a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/26 09:35 linux-6.6.y d1cfde2d5d15 7ff32d8b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/22 12:08 linux-6.6.y d1cfde2d5d15 43bfcdb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/21 19:32 linux-6.6.y d1cfde2d5d15 43bfcdb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/20 00:20 linux-6.6.y d1cfde2d5d15 43bfcdb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/19 12:46 linux-6.6.y 924b4a879cbb 570c59ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/19 00:13 linux-6.6.y 924b4a879cbb a776b0d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/18 08:16 linux-6.6.y 924b4a879cbb b62b3ded .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/14 11:49 linux-6.6.y 924b4a879cbb 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/14 11:39 linux-6.6.y 924b4a879cbb 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/13 16:58 linux-6.6.y 924b4a879cbb 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/13 01:30 linux-6.6.y 924b4a879cbb 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/10 11:15 linux-6.6.y 924b4a879cbb 34dab4be .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/06/04 09:16 linux-6.6.y 924b4a879cbb 197909be .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/27 05:10 linux-6.6.y 0a40c6fbd105 2b01f00e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/26 07:16 linux-6.6.y 0a40c6fbd105 c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/22 17:30 linux-6.6.y eac8889a3a1c 5f091fcc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/21 23:11 linux-6.6.y eac8889a3a1c e195359d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/21 08:49 linux-6.6.y eac8889a3a1c 41b8c833 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/21 08:49 linux-6.6.y eac8889a3a1c 41b8c833 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/21 07:15 linux-6.6.y eac8889a3a1c 41b8c833 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/20 09:13 linux-6.6.y eac8889a3a1c 0909d65f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/20 03:30 linux-6.6.y eac8889a3a1c 0909d65f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/18 06:40 linux-6.6.y eac8889a3a1c de5aae85 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/15 07:11 linux-6.6.y 3b9f64db0496 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/14 05:48 linux-6.6.y 3b9f64db0496 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/14 03:00 linux-6.6.y 3b9f64db0496 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/12 15:07 linux-6.6.y 3b9f64db0496 07aeade5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/11 14:38 linux-6.6.y 3b9f64db0496 845acb1c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/10 20:03 linux-6.6.y 3b9f64db0496 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/10 00:41 linux-6.6.y 3b9f64db0496 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/09 11:03 linux-6.6.y 3b9f64db0496 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/09 00:54 linux-6.6.y 3b9f64db0496 b2988c17 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in read_part_sector
2026/05/09 00:53 linux-6.6.y 3b9f64db0496 b2988c17 .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.