syzbot


INFO: task hung in read_part_sector (2)

Status: upstream: reported on 2024/08/04 19:22
Subsystems: block
[Documentation on labels]
Reported-by: syzbot+82de77d3f217960f087d@syzkaller.appspotmail.com
First crash: 492d, last: 2h11m
Discussions (7)
Title Replies (including bot) Last reply
[syzbot] Monthly block report (Aug 2025) 0 (1) 2025/08/27 08:15
[syzbot] Monthly block report (Jul 2025) 0 (1) 2025/07/27 10:41
[syzbot] Monthly block report (Jun 2025) 0 (1) 2025/06/26 05:36
[syzbot] Monthly block report (Apr 2025) 0 (1) 2025/04/24 13:06
[syzbot] Monthly block report (Mar 2025) 0 (1) 2025/03/24 18:56
[syzbot] Monthly block report (Oct 2024) 0 (1) 2024/10/16 15:35
[syzbot] [block?] INFO: task hung in read_part_sector (2) 0 (1) 2024/08/04 19:22
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 224 2d01h 789d 0/3 upstream: reported C repro on 2023/07/29 13:11
linux-6.1 INFO: task hung in read_part_sector 1 1 597d 597d 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 612d 679d 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 40 1d04h 98d 0/2 upstream: reported on 2025/06/19 22:23
linux-6.1 INFO: task hung in read_part_sector (2) 1 1 475d 475d 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 1 59d 59d 0/3 upstream: reported on 2025/07/28 11:29

Sample crash report:
INFO: task udevd:5928 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:22600 pid:5928  tgid:5928  ppid:5228   task_flags:0x400140 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5357 [inline]
 __schedule+0x1798/0x4cc0 kernel/sched/core.c:6961
 __schedule_loop kernel/sched/core.c:7043 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:7058
 io_schedule+0x80/0xd0 kernel/sched/core.c:7903
 folio_wait_bit_common+0x6b0/0xb90 mm/filemap.c:1317
 folio_put_wait_locked mm/filemap.c:1481 [inline]
 do_read_cache_folio+0x1aa/0x590 mm/filemap.c:3939
 read_mapping_folio include/linux/pagemap.h:991 [inline]
 read_part_sector+0xb6/0x2b0 block/partitions/core.c:722
 adfspart_check_POWERTEC+0x8c/0xf30 block/partitions/acorn.c:454
 check_partition block/partitions/core.c:141 [inline]
 blk_add_partitions block/partitions/core.c:589 [inline]
 bdev_disk_changed+0x75f/0x14b0 block/partitions/core.c:693
 blkdev_get_whole+0x380/0x510 block/bdev.c:748
 bdev_open+0x31e/0xd30 block/bdev.c:957
 blkdev_open+0x457/0x600 block/fops.c:694
 do_dentry_open+0x953/0x13f0 fs/open.c:965
 vfs_open+0x3b/0x340 fs/open.c:1095
 do_open fs/namei.c:3887 [inline]
 path_openat+0x2ee5/0x3830 fs/namei.c:4046
 do_filp_open+0x1fa/0x410 fs/namei.c:4073
 do_sys_openat2+0x121/0x1c0 fs/open.c:1435
 do_sys_open fs/open.c:1450 [inline]
 __do_sys_openat fs/open.c:1466 [inline]
 __se_sys_openat fs/open.c:1461 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1461
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa770ea7407
RSP: 002b:00007fff7253bf00 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fa77158c880 RCX: 00007fa770ea7407
RDX: 00000000000a0800 RSI: 000055f837705860 RDI: ffffffffffffff9c
RBP: 000055f8376f9910 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000055f83770dfa0
R13: 000055f837707190 R14: 0000000000000000 R15: 000055f83770dfa0
 </TASK>

Showing all locks held in the system:
3 locks held by kworker/0:0/9:
1 lock held by khungtaskd/31:
 #0: ffffffff8e13a0e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e13a0e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e13a0e0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
2 locks held by getty/5616:
 #0: ffff88814cb8f0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900036bb2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
1 lock held by udevd/5928:
 #0: ffff888025308358 (&disk->open_mutex){+.+.}-{4:4}, at: bdev_open+0xe0/0xd30 block/bdev.c:945
2 locks held by kworker/u8:8/5995:
 #0: ffff8880b8639f98 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:636
 #1: ffffc90004f3fbc0 ((work_completion)(&(&kfence_timer)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc90004f3fbc0 ((work_completion)(&(&kfence_timer)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3319
3 locks held by kworker/u8:9/6063:
 #0: ffff88802fb4d948 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff88802fb4d948 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3319
 #1: ffffc900050a7bc0 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc900050a7bc0 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3319
 #2: ffffffff8f53a248 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff8f53a248 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x112/0x14b0 net/ipv6/addrconf.c:4194
1 lock held by udevd/6733:
 #0: ffff88801b2f7988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_dop_revalidate+0x9e/0x5d0 fs/kernfs/dir.c:1180
3 locks held by kworker/1:10/7587:
 #0: ffff8881442da548 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3211 [inline]
 #0: ffff8881442da548 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3319
 #1: ffffc90003cafbc0 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3212 [inline]
 #1: ffffc90003cafbc0 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3319
 #2: ffff8880286ca198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:911 [inline]
 #2: ffff8880286ca198 (&dev->mutex){....}-{4:4}, at: hub_event+0x184/0x4a20 drivers/usb/core/hub.c:5898
3 locks held by syz-executor/13946:
 #0: ffffffff8f53a248 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff8f53a248 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock net/core/rtnetlink.c:341 [inline]
 #0: ffffffff8f53a248 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x8db/0x1c70 net/core/rtnetlink.c:4056
 #1: ffff88801c3894e8 (&wg->device_update_lock){+.+.}-{4:4}, at: wg_open+0x227/0x420 drivers/net/wireguard/device.c:50
 #2: ffffffff8e13fb78 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:311 [inline]
 #2: ffffffff8e13fb78 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x2f6/0x730 kernel/rcu/tree_exp.h:957
2 locks held by syz.0.2755/14145:

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 31 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:328 [inline]
 watchdog+0xf93/0xfe0 kernel/hung_task.c:491
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 5995 Comm: kworker/u8:8 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:__lock_acquire+0x2d/0xd20 kernel/locking/lockdep.c:5093
Code: 41 56 41 55 41 54 53 48 83 ec 30 48 89 fb 65 48 8b 3c 25 08 e0 a0 92 45 31 ff 83 3d dc 76 06 0e 00 0f 84 7e 0c 00 00 48 8b 03 <48> 3d 20 a3 64 93 0f 84 6f 0c 00 00 41 89 cc 41 89 d6 8b 0d 3b 4b
RSP: 0018:ffffc90000007c30 EFLAGS: 00000002
RAX: ffffffff99b07740 RBX: ffffffff99b07388 RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888025e30000
RBP: ffffffff81ae5da0 R08: 0000000000000001 R09: 0000000000000001
R10: dffffc0000000000 R11: fffff52000000fb0 R12: 0000000000000002
R13: ffffffff99b07388 R14: 0000000000000001 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff888125c12000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff72534fc8 CR3: 000000005bc60000 CR4: 0000000000350ef0
Call Trace:
 <IRQ>
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 seqcount_lockdep_reader_access+0xc9/0x1c0 include/linux/seqlock.h:72
 ktime_get_update_offsets_now+0x60/0x3d0 kernel/time/timekeeping.c:2556
 hrtimer_update_base kernel/time/hrtimer.c:640 [inline]
 hrtimer_interrupt+0x132/0xaa0 kernel/time/hrtimer.c:1869
 local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1039 [inline]
 __sysvec_apic_timer_interrupt+0x10b/0x410 arch/x86/kernel/apic/apic.c:1056
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline]
 sysvec_apic_timer_interrupt+0xa1/0xc0 arch/x86/kernel/apic/apic.c:1050
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
RIP: 0010:console_trylock_spinning kernel/printk/printk.c:2061 [inline]
RIP: 0010:vprintk_emit+0x58f/0x7a0 kernel/printk/printk.c:2449
Code: 85 32 01 00 00 e8 51 86 1f 00 41 89 df 4d 85 f6 48 8b 1c 24 75 07 e8 40 86 1f 00 eb 06 e8 39 86 1f 00 fb 48 c7 c7 80 e3 12 8e <31> f6 ba 01 00 00 00 31 c9 41 b8 01 00 00 00 45 31 c9 53 e8 b9 35
RSP: 0018:ffffc90004f3f680 EFLAGS: 00000293
RAX: ffffffff81a02887 RBX: ffffffff81a02744 RCX: ffff888025e30000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8e12e380
RBP: ffffc90004f3f790 R08: ffffffff8fa3a837 R09: 1ffffffff1f47506
R10: dffffc0000000000 R11: fffffbfff1f47507 R12: dffffc0000000000
R13: 1ffff920009e7ed4 R14: 0000000000000200 R15: 000000000000003f
 _printk+0xcf/0x120 kernel/printk/printk.c:2475
 ieee80211_sta_find_ibss net/mac80211/ibss.c:1443 [inline]
 ieee80211_ibss_work+0xdae/0x1060 net/mac80211/ibss.c:1662
 cfg80211_wiphy_work+0x2bb/0x470 net/wireless/core.c:435
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3319
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (3226):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/26 06:26 upstream 4ff71af020ae 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in read_part_sector
2025/09/25 14:10 upstream bf40f4b87761 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in read_part_sector
2025/09/25 08:37 upstream 4ea5af085908 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in read_part_sector
2025/09/25 05:25 upstream 4ea5af085908 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in read_part_sector
2025/09/23 23:56 upstream cec1e6e5d1ab 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2025/03/02 00:05 upstream 03d38806a902 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in read_part_sector
2024/07/31 19:09 upstream e4fc196f5ba3 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2024/07/24 08:02 upstream 28bbe4ea686a 57b2edb1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in read_part_sector
2025/09/26 02:16 net d9c70e93ec59 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/26 00:10 net d9c70e93ec59 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/25 18:58 net d9c70e93ec59 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/25 15:12 net b7e32ae66642 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/25 11:03 net b7e32ae66642 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/25 06:31 net b7e32ae66642 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/25 01:35 net 181d981b14bf 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/24 19:22 net 181d981b14bf 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/24 14:54 net 181d981b14bf 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/24 13:27 net ca9f9cdc4de9 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/24 09:40 net ca9f9cdc4de9 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/24 08:08 net ca9f9cdc4de9 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/24 05:35 net ca9f9cdc4de9 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/24 04:34 net ca9f9cdc4de9 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/24 01:02 net ca9f9cdc4de9 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/23 20:19 net 3d3aa9472c6d 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/23 16:45 net 3d3aa9472c6d 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/23 13:21 net 3d3aa9472c6d 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/23 05:01 net 3491bb7dae5c 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/22 23:45 net 3491bb7dae5c 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/22 20:46 net 3491bb7dae5c 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/22 15:18 net b65678cacc03 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce INFO: task hung in read_part_sector
2025/09/26 04:47 net-next 203e3beb73e5 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/26 03:44 net-next 203e3beb73e5 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/26 03:16 net-next 203e3beb73e5 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/25 20:56 net-next 12de5f0f6c2d 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/25 17:24 net-next 12de5f0f6c2d 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/25 07:32 net-next 5e3fee34f626 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/24 22:55 net-next dc1dea796b19 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/24 21:24 net-next dc1dea796b19 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/24 16:19 net-next dc1dea796b19 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/24 11:56 net-next dc1dea796b19 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/24 10:46 net-next dc1dea796b19 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/24 06:38 net-next df1526752e0c 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/24 01:35 net-next df1526752e0c 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/23 21:34 net-next df1526752e0c 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/23 18:31 net-next 3afb106f3f9a 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/23 15:27 net-next 3afb106f3f9a 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/23 12:00 net-next 3afb106f3f9a 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/23 11:43 net-next 3afb106f3f9a 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/23 10:01 net-next 3afb106f3f9a 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/23 08:15 net-next 78e87f9d5358 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce INFO: task hung in read_part_sector
2025/09/25 04:00 linux-next b5a4da2c459f 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in read_part_sector
2025/09/22 17:12 linux-next 846bd2225ec3 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in read_part_sector
2025/09/22 16:01 linux-next 846bd2225ec3 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in read_part_sector
* Struck through repros no longer work on HEAD.