syzbot

 sign-in | mailing list | source | docs | 🏰
🐞 Open [1344]
≡ Subsystems
🐞 Fixed [7090]
🐞 Invalid [18714]
⬇ Missing Backports [220]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
✨ AI
💬 Send us feedback

INFO: task hung in blk_trace_setup (4)

Status: upstream: reported syz repro on 2025/07/15 17:43
Subsystems: block trace
[Documentation on labels]
Reported-by: syzbot+9c1ebb9957045e00ac63@syzkaller.appspotmail.com
First crash: 418d, last: 1d15h
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision Error
f23dc134-0a1e-465d-8cbf-24943181cdaa assessment-security 💥 INFO: task hung in blk_trace_setup (4) 2026/05/15 05:16 2026/05/15 05:16 2026/05/15 05:18 6ccb967e465e832a7bfd7a116ad00d52a0923a5d failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "32" "ARCH=x86_64" "CC=ccache clang" "LD=ld.lld" "O=/app/workdir/cache/build/12861394d545e079985e9351bff4022fe9cca063" "-s" "bzImage" "compile_commands.json"]: exit status 2 * * Restart config... * * * General architecture-dependent options * SMT (Hyperthreading) scheduler support (SCHED_SMT) [Y/?] y Cluster scheduler support (SCHED_CLUSTER) [Y/n/?] y Multi-Core Cache (MC) scheduler support (SCHED_MC) [Y/n/?] y Kprobes (KPROBES) [N/y/?] n Optimize very unlikely/likely branches (JUMP_LABEL) [Y/n/?] y Static key selftest (STATIC_KEYS_SELFTEST) [N/y/?] n Static call selftest (STATIC_CALL_SELFTEST) [N/y/?] n Enable seccomp to safely execute untrusted bytecode (SECCOMP) [Y/n/?] y Show seccomp filter cache status in /proc/pid/seccomp_cache (SECCOMP_CACHE_DEBUG) [N/y/?] n Stack Protector buffer overflow detection (STACKPROTECTOR) [Y/n/?] y Strong Stack Protector (STACKPROTECTOR_STRONG) [Y/n/?] y Link Time Optimization (LTO) > 1. None (LTO_NONE) choice[1]: 1 Enable Clang's AutoFDO build (EXPERIMENTAL) (AUTOFDO_CLANG) [N/y/?] (NEW) Error in reading or end of file. Enable Clang's Propeller build (PROPELLER_CLANG) [N/y/?] (NEW) Error in reading or end of file. Use Kernel Control Flow Integrity (kCFI) (CFI) [N/y/?] (NEW) Error in reading or end of file. Number of bits to use for ASLR of mmap base address (ARCH_MMAP_RND_BITS) [28] 28 Number of bits to use for ASLR of mmap base address for compatible applications (ARCH_MMAP_RND_COMPAT_BITS) [8] 8 MMU page size > 1. 4KiB pages (PAGE_SIZE_4KB) choice[1]: 1 Provide system calls for 32-bit time_t (COMPAT_32BIT_TIME) [Y/n/?] y Use a virtually-mapped stack (VMAP_STACK) [Y/n/?] y Support for randomizing kernel stack offset on syscall entry (RANDOMIZE_KSTACK_OFFSET) [Y/n/?] y Default state of kernel stack offset randomization (RANDOMIZE_KSTACK_OFFSET_DEFAULT) [N/y/?] n Locking event counts collection (LOCK_EVENT_COUNTS) [N/y/?] n * * Memory initialization * Initialize kernel stack variables at function entry 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE) 2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) > 3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) choice[1-3?]: 3 Poison kernel stack before returning from syscalls (KSTACK_ERASE) [N/y/?] (NEW) Error in reading or end of file. Enable heap memory zeroing on allocation by default (INIT_ON_ALLOC_DEFAULT_ON) [Y/n/?] y Enable heap memory zeroing on free by default (INIT_ON_FREE_DEFAULT_ON) [N/y/?] n Enable register zeroing on function exit (ZERO_CALL_USED_REGS) [N/y/?] n * * Kernel hardening options * Randomize layout of sensitive kernel structures > 1. Disable structure layout randomization (RANDSTRUCT_NONE) 2. Fully randomize structure layout (RANDSTRUCT_FULL) (NEW) choice[1-2?]: Error in reading or end of file. /app/workdir/cache/src/8bc6af835ed10de45097c2b4bd65c27d2b0db088/security/apparmor/apparmorfs.c:177:28: warning: unused function 'get_loaddata_common_ref' [-Wunused-function] 177 | static struct aa_loaddata *get_loaddata_common_ref(struct aa_common_ref *ref) | ^~~~~~~~~~~~~~~~~~~~~~~ 1 warning generated. /app/workdir/cache/src/8bc6af835ed10de45097c2b4bd65c27d2b0db088/sound/usb/mixer_s1810c.c:633:5: warning: stack frame size (2360) exceeds limit (2048) in 'snd_sc1810_init_mixer' [-Wframe-larger-than] 633 | int snd_sc1810_init_mixer(struct usb_mixer_interface *mixer) | ^ 1 warning generated. fixdep: not all data was written to the output make[5]: *** [/app/workdir/cache/src/8bc6af835ed10de45097c2b4bd65c27d2b0db088/scripts/Makefile.build:289: drivers/dma/dmaengine.o] Error 1 make[5]: *** Deleting file 'drivers/dma/dmaengine.o' make[4]: *** [/app/workdir/cache/src/8bc6af835ed10de45097c2b4bd65c27d2b0db088/scripts/Makefile.build:548: drivers/dma] Error 2 make[4]: *** Waiting for unfinished jobs.... fixdep: not all data was written to the output make[4]: *** [/app/workdir/cache/src/8bc6af835ed10de45097c2b4bd65c
Cause bisection: introduced by (bisect log) :
commit c2368b19807affd7621f7c4638cd2e17fec13021
Author: Jiri Pirko <jiri@nvidia.com>
Date: Fri Jul 29 07:10:35 2022 +0000

  net: devlink: introduce "unregistering" mark and use it during devlinks iteration

Crash: INFO: rcu detected stall in corrupted (log)
Repro: syz .config
  
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Discussions (6)
Title Replies (including bot) Last reply
[syzbot] Monthly trace report (Mar 2026) 0 (1) 2026/03/26 12:34
[syzbot] Monthly trace report (Dec 2025) 0 (1) 2025/12/22 13:07
[syzbot] Monthly trace report (Oct 2025) 0 (1) 2025/10/21 08:02
[syzbot] [block?] [trace?] INFO: task hung in blk_trace_setup (4) 0 (2) 2025/09/28 20:12
[syzbot] Monthly trace report (Aug 2025) 0 (1) 2025/08/20 08:11
[syzbot] Monthly trace report (Jul 2025) 0 (1) 2025/07/20 09:04
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in blk_trace_setup (2) 1 syz 1 6d19h 6d19h 0/3 upstream: reported syz repro on 2026/05/09 00:50
linux-5.15 INFO: task hung in blk_trace_setup 1 1 229d 229d 0/3 auto-obsoleted due to no activity on 2026/01/05 22:14
upstream INFO: task hung in blk_trace_setup (2) block trace 1 1 2247d 2247d 0/29 auto-closed as invalid on 2020/06/18 13:53
upstream INFO: task hung in blk_trace_setup (3) block trace 1 1 791d 791d 0/29 auto-obsoleted due to no activity on 2024/06/13 01:38
upstream INFO: task hung in blk_trace_setup trace block 1 1 2619d 2619d 0/29 auto-closed as invalid on 2019/09/10 19:17
▶ ▼ Last patch testing requests (7)
Created Duration User Patch Repo Result
2026/05/09 17:48 35m retest repro linux-next report log
2026/04/25 04:25 28m retest repro upstream report log
2026/04/24 17:27 22m retest repro upstream report log
2026/03/17 21:23 3h16m retest repro upstream report log
2025/12/24 11:00 26m retest repro upstream report log
2025/10/11 00:11 19m retest repro upstream report log
2025/08/01 01:55 22m retest repro upstream report log
▶ ▼ Cause bisection attempts (3)
Created Duration User Patch Repo Result
2025/09/28 08:44 11h26m bisect upstream OK (1) job log log
2025/08/06 11:27 5h44m bisect upstream error job log
2025/07/28 10:28 5h57m bisect upstream error job log

Sample crash report:
INFO: task syz.4.21:6291 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.21        state:D stack:27208 pid:6291  tgid:6291  ppid:6264   task_flags:0x480140 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5298 [inline]
 __schedule+0xfee/0x6120 kernel/sched/core.c:6911
 __schedule_loop kernel/sched/core.c:6993 [inline]
 schedule+0xdd/0x390 kernel/sched/core.c:7008
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7065
 __mutex_lock_common kernel/locking/mutex.c:692 [inline]
 __mutex_lock+0xc9a/0x1b90 kernel/locking/mutex.c:776
 blk_debugfs_lock_nomemsave block/blk.h:740 [inline]
 blk_debugfs_lock block/blk.h:752 [inline]
 blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
 blk_trace_ioctl+0x245/0x320 kernel/trace/blktrace.c:937
 blkdev_ioctl+0x17c/0x6f0 block/ioctl.c:793
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f53fd99c819
RSP: 002b:00007ffc2ca88c58 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f53fdc15fa0 RCX: 00007f53fd99c819
RDX: 00002000000000c0 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007f53fda32c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f53fdc15fac R14: 00007f53fdc15fa0 R15: 00007f53fdc15fa0
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/32:
 #0: ffffffff8e7e7760 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:312 [inline]
 #0: ffffffff8e7e7760 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:850 [inline]
 #0: ffffffff8e7e7760 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x3d/0x184 kernel/locking/lockdep.c:6775
5 locks held by kworker/u8:3/49:
 #0: ffff8880b853b360 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2c/0x140 kernel/sched/core.c:647
 #1: ffff8880b8524648 (psi_seq){-.-.}-{0:0}, at: psi_sched_switch kernel/sched/stats.h:225 [inline]
 #1: ffff8880b8524648 (psi_seq){-.-.}-{0:0}, at: __schedule+0x2c11/0x6120 kernel/sched/core.c:6905
 #2: ffff8880b8526358 (&base->lock){-.-.}-{2:2}, at: lock_timer_base+0x124/0x1d0 kernel/time/timer.c:1004
 #3: ffff888155b78168 (&rdev->bss_lock){+.-.}-{3:3}, at: spin_lock_bh include/linux/spinlock.h:347 [inline]
 #3: ffff888155b78168 (&rdev->bss_lock){+.-.}-{3:3}, at: ieee80211_ibss_work+0x153/0x1050 net/mac80211/ibss.c:1651
 #4: ffff8880b853b360 (&rq->__lock){-.-.}-{2:2}, at: finish_lock_switch kernel/sched/core.c:5033 [inline]
 #4: ffff8880b853b360 (&rq->__lock){-.-.}-{2:2}, at: finish_task_switch.isra.0+0x14a/0xb80 kernel/sched/core.c:5153
4 locks held by kworker/u8:7/1294:
2 locks held by getty/5584:
 #0: ffff888038b3a0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc900033332f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x419/0x1500 drivers/tty/n_tty.c:2211
2 locks held by syz.3.20/6191:
1 lock held by syz.4.21/6291:
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:740 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:752 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.5.22/6322:
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:740 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:752 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.6.23/6416:
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:740 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:752 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.7.24/6510:
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:740 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:752 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.8.25/6537:
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:740 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:752 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.9.26/6632:
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:740 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:752 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.0.27/6746:
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:740 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:752 [inline]
 #0: ffff88802753af00 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
2 locks held by syz.1.63/7104:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 32 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 nmi_cpu_backtrace.cold+0x12d/0x151 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x1d7/0x230 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:161 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x141/0x190 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:346 [inline]
 watchdog+0xd25/0x1050 kernel/hung_task.c:515
 kthread+0x370/0x450 kernel/kthread.c:436
 ret_from_fork+0x754/0xd80 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 58 Comm: kworker/u8:4 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x70 kernel/kcov.c:210
Code: 86 0d 5a 00 48 89 df 5b e9 1d 8b 5f 00 be 03 00 00 00 5b e9 e2 69 ec 02 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 <f3> 0f 1e fa 65 8b 05 a5 bc 05 12 48 8b 34 24 65 48 8b 15 81 bc 05
RSP: 0018:ffffc900015f7910 EFLAGS: 00000083
RAX: 0000000000000000 RBX: ffff88813fe9a558 RCX: ffffffff81ac70bc
RDX: 0000000000000cae RSI: 0000000000001000 RDI: ffff88801c750000
RBP: ffffffff82683cad R08: 0000000000000007 R09: 0000000000001000
R10: 0000000000000cae R11: 0000000000000000 R12: 0000000000000cae
R13: 8000000002683063 R14: 0000000000000001 R15: 8000000000000063
FS:  0000000000000000(0000) GS:ffff888124440000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffa17b2ba40 CR3: 000000000e598000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 __text_poke+0x3ce/0xae0 arch/x86/kernel/alternative.c:2589
 smp_text_poke_batch_finish+0x6b5/0xc60 arch/x86/kernel/alternative.c:3049
 arch_jump_label_transform_apply+0x1c/0x30 arch/x86/kernel/jump_label.c:146
 jump_label_update+0x37a/0x550 kernel/jump_label.c:919
 static_key_enable_cpuslocked+0x1bc/0x270 kernel/jump_label.c:210
 static_key_enable+0x1a/0x20 kernel/jump_label.c:223
 toggle_allocation_gate mm/kfence/core.c:900 [inline]
 toggle_allocation_gate+0xfe/0x2d0 mm/kfence/core.c:892
 process_one_work+0xa23/0x19a0 kernel/workqueue.c:3276
 process_scheduled_works kernel/workqueue.c:3359 [inline]
 worker_thread+0x5ef/0xe50 kernel/workqueue.c:3440
 kthread+0x370/0x450 kernel/kthread.c:436
 ret_from_fork+0x754/0xd80 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (25):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/09 09:55 upstream 7f87a5ea75f0 38c8e246 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in blk_trace_setup
2026/02/28 03:21 upstream aed968f8a6cd 2cf092b8 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2025/07/14 23:04 upstream 347e9f5043c8 03fcfc4b .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2026/05/14 04:54 linux-next e98d21c170b0 6ccb967e .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in blk_trace_setup
2026/04/04 18:54 linux-next cc13002a9f98 4440e7c2 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in blk_trace_setup
2026/05/12 02:54 upstream 50897c955902 d168f260 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in blk_trace_setup
2026/04/10 17:22 upstream 9a9c8ce300cd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in blk_trace_setup
2026/04/09 06:43 upstream 7f87a5ea75f0 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in blk_trace_setup
2026/04/04 13:41 upstream 7ca6d1cfec80 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2026/03/20 20:44 upstream 0e4f8f1a3d08 85bf2a64 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in blk_trace_setup
2026/03/18 21:39 upstream a989fde763f4 0199f9a1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in blk_trace_setup
2026/03/03 20:40 upstream af4e9ef3d784 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in blk_trace_setup
2026/02/28 00:12 upstream aed968f8a6cd 2cf092b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2026/01/08 13:20 upstream f0b9d8eb98df d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2025/12/06 22:34 upstream 416f99c3b16f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2025/09/05 12:52 upstream d69eb204c255 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in blk_trace_setup
2025/08/18 01:34 upstream 038d61fd6422 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in blk_trace_setup
2025/07/17 17:11 upstream e2291551827f 0d1223f1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2025/06/27 20:31 upstream 67a993863163 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2025/06/27 09:22 upstream e34a79b96ab9 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2025/06/10 22:38 upstream f09079bd04a9 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2025/06/02 10:41 upstream cd2e103d57e5 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in blk_trace_setup
2025/12/10 10:59 upstream c9b47175e913 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in blk_trace_setup
2025/03/23 15:40 upstream 586de92313fc 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in blk_trace_setup
2026/02/23 22:01 linux-next d4906ae14a5f 305c0ec5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in blk_trace_setup
* Struck through repros no longer work on HEAD.