syzbot


INFO: task hung in blk_trace_setup (4)

Status: upstream: reported syz repro on 2025/07/15 17:43
Subsystems: block trace
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+9c1ebb9957045e00ac63@syzkaller.appspotmail.com
First crash: 457d, last: 12d
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)
  
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision Error
21b7c1eb-8c5f-495e-878a-06578896b66b assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ INFO: task hung in blk_trace_setup (4) 2026/05/31 15:04 2026/05/31 15:04 2026/05/31 16:11 6b4a844333e83556da95d61d7f207e7ef5cd4bc6

			
		
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/12861394d545e07998...
truncated to first 200 bytes; open job for full error
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) origin:upstream 1 syz error 1 45d 45d 0/3 upstream: reported syz repro on 2026/05/09 00:50
linux-5.15 INFO: task hung in blk_trace_setup 1 1 268d 268d 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 2286d 2286d 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 830d 830d 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 2658d 2657d 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.5.22:6267 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.5.22        state:D stack:28808 pid:6267  tgid:6266  ppid:6205   task_flags:0x480040 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x1295/0x67a0 kernel/sched/core.c:7189
 __schedule_loop kernel/sched/core.c:7268 [inline]
 schedule+0xdd/0x390 kernel/sched/core.c:7283
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7340
 __mutex_lock_common kernel/locking/mutex.c:726 [inline]
 __mutex_lock+0xced/0x1b10 kernel/locking/mutex.c:820
 blk_debugfs_lock_nomemsave block/blk.h:758 [inline]
 blk_debugfs_lock block/blk.h:770 [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:786
 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+0x115/0x840 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f15b679ce59
RSP: 002b:00007f15b76cb028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f15b6a15fa0 RCX: 00007f15b679ce59
RDX: 00002000000000c0 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007f15b6832d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f15b6a16038 R14: 00007f15b6a15fa0 R15: 00007ffd4ebfd548
 </TASK>

Showing all locks held in the system:
3 locks held by kworker/0:0/9:
 #0: ffff88813fe57140 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x12d6/0x1980 kernel/workqueue.c:3289
 #1: ffffc900000e7d08 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x973/0x1980 kernel/workqueue.c:3290
 #2: ffff888022a8f250 (&data->fib_lock){+.+.}-{4:4}, at: nsim_fib_event_work+0x1b8/0x63b0 drivers/net/netdevsim/fib.c:1490
4 locks held by kworker/u8:1/13:
1 lock held by khungtaskd/31:
 #0: ffffffff8e7e53e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8e7e53e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8e7e53e0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x3d/0x184 kernel/locking/lockdep.c:6775
2 locks held by getty/5396:
 #0: ffff8880381500a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000322b2e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x419/0x14f0 drivers/tty/n_tty.c:2211
3 locks held by syz-execprog/5676:
7 locks held by syz.4.21/6202:
1 lock held by syz.5.22/6267:
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:758 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:770 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.6.23/6424:
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:758 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:770 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.7.24/6470:
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:758 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:770 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.8.25/6579:
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:758 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:770 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.9.26/6691:
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:758 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:770 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.0.27/6772:
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:758 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:770 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz.1.28/7026:
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock_nomemsave block/blk.h:758 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_debugfs_lock block/blk.h:770 [inline]
 #0: ffff888026f1ade8 (&q->debugfs_mutex){+.+.}-{4:4}, at: blk_trace_setup+0x1f2/0x440 kernel/trace/blktrace.c:788
1 lock held by syz-executor/7188:
 #0: ffffffff8e7f0f28 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock+0x27f/0x3c0 kernel/rcu/tree_exp.h:311
4 locks held by dhcpcd-run-hook/7288:

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

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 04/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:162 [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:353 [inline]
 watchdog+0xcb1/0x1030 kernel/hung_task.c:561
 kthread+0x370/0x450 kernel/kthread.c:436
 ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158
 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: 6590 Comm: kworker/u8:3 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:__sanitizer_cov_trace_switch+0x3b/0x90 kernel/kcov.c:351
Code: 53 48 8b 46 08 48 83 f8 20 74 63 77 48 48 83 f8 08 74 63 41 be 03 00 00 00 48 83 f8 10 75 29 4c 8b 6d 00 31 db 4d 85 ed 74 1e <48> 8b 74 dd 10 48 8b 4c 24 28 4c 89 e2 4c 89 f7 48 83 c3 01 e8 8c
RSP: 0018:ffffc90002ea75a8 EFLAGS: 00000212
RAX: 0000000000000000 RBX: 000000000000000d RCX: ffffffff8b0b3032
RDX: 0000000000000032 RSI: 000000000000005a RDI: ffff888034371f00
RBP: ffffffff8d1cdfe0 R08: 0000000000000001 R09: 000000000000005a
R10: 0000000000000032 R11: ffff8881bf1c6000 R12: 0000000000000032
R13: 0000000000000020 R14: 0000000000000001 R15: ffff8881d7610d8d
FS:  0000000000000000(0000) GS:ffff88812438a000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f47854ac4e8 CR3: 000000022f922000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 _ieee802_11_parse_elems_full+0x2f2/0x4d60 net/mac80211/parse.c:355
 ieee802_11_parse_elems_full+0x1175/0x37f0 net/mac80211/parse.c:1120
 ieee802_11_parse_elems net/mac80211/ieee80211_i.h:2518 [inline]
 ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1565 [inline]
 ieee80211_ibss_rx_queued_mgmt+0xc8d/0x2f80 net/mac80211/ibss.c:1596
 ieee80211_iface_process_skb net/mac80211/iface.c:1795 [inline]
 ieee80211_iface_work+0xbff/0x13e0 net/mac80211/iface.c:1849
 cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513
 process_one_work+0xa0e/0x1980 kernel/workqueue.c:3314
 process_scheduled_works kernel/workqueue.c:3397 [inline]
 worker_thread+0x5ef/0xe50 kernel/workqueue.c:3478
 kthread+0x370/0x450 kernel/kthread.c:436
 ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (31):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/05/31 09:46 upstream 9d87d0fc8c8e 6b4a8443 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in blk_trace_setup
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/16 05:36 linux-next e98d21c170b0 81fb92f3 .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/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/06/11 08:46 upstream 9716c086c8e8 b754d2d8 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in blk_trace_setup
2026/05/31 05:21 upstream 9d87d0fc8c8e 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in blk_trace_setup
2026/05/28 08:56 upstream eb3f4b7426cf 4c36e7e5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-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
2026/05/24 15:44 upstream 4cbfe4502e3d c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 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.