syzbot


WARNING in tracing_start_tr

Status: upstream: reported on 2025/04/17 00:22
Subsystems: trace
[Documentation on labels]
Reported-by: syzbot+ccdec3bfe0beec58a38d@syzkaller.appspotmail.com
First crash: 53d, last: 2d08h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [trace?] WARNING in tracing_start_tr 0 (1) 2025/04/17 00:22

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 14350 at kernel/trace/trace.c:2526 tracing_start_tr.part.0+0x1fc/0x2a0 kernel/trace/trace.c:2526
Modules linked in:
CPU: 0 UID: 0 PID: 14350 Comm: syz.0.1631 Not tainted 6.15.0-syzkaller-11061-g7f9039c524a3 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:tracing_start_tr.part.0+0x1fc/0x2a0 kernel/trace/trace.c:2526
Code: 00 0f 85 97 00 00 00 48 83 3d cf 4f 62 0c 00 74 78 e8 38 55 fb ff 4c 89 ff e8 60 26 bc 09 90 e9 d9 fe ff ff e8 25 55 fb ff 90 <0f> 0b 90 c7 83 94 00 00 00 00 00 00 00 e9 c1 fe ff ff e8 4d 41 61
RSP: 0018:ffffc900033b7be8 EFLAGS: 00010087
RAX: 0000000000003524 RBX: ffffffff8e449920 RCX: ffffc9000d850000
RDX: 0000000000080000 RSI: ffffffff81c0289b RDI: 0000000000000005
RBP: 00000000ffffffff R08: 0000000000000005 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000001 R12: 1ffff92000676f7e
R13: 0000000000000287 R14: ffffffff8e449a00 R15: ffffffff8e449940
FS:  00007fa62f0976c0(0000) GS:ffff888124973000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b308d7ff8 CR3: 000000007755e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 tracing_start_tr kernel/trace/trace.c:9585 [inline]
 buffer_subbuf_size_write+0x226/0x280 kernel/trace/trace.c:9583
 vfs_write+0x29d/0x1150 fs/read_write.c:684
 ksys_write+0x12a/0x250 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa62e18e969
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa62f097038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fa62e3b6080 RCX: 00007fa62e18e969
RDX: 000000000000fdef RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007fa62e210ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fa62e3b6080 R15: 00007ffd04d903d8
 </TASK>

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/02 22:40 upstream 7f9039c524a3 a30356b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto WARNING in tracing_start_tr
2025/06/02 05:37 upstream cd2e103d57e5 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto WARNING in tracing_start_tr
2025/05/19 06:01 upstream a5806cd506af f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto WARNING in tracing_start_tr
2025/04/23 21:36 upstream a79be02bba5c 9882047a .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto WARNING in tracing_start_tr
2025/04/13 00:18 upstream 3bde70a2c827 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto WARNING in tracing_start_tr
* Struck through repros no longer work on HEAD.