syzbot

 sign-in | mailing list | source | docs
🐞 Open [929] ≡ Subsystems 🐞 Fixed [4767] 🐞 Invalid [11224] ⬇ Missing Backports [28] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

WARNING in get_probe_ref

Status: upstream: reported C repro on 2020/05/18 03:12
Subsystems: block trace
[Documentation on labels]
Reported-by: syzbot+8672dcb9d10011c0a160@syzkaller.appspotmail.com
First crash: 1229d, last: 22d
Cause bisection: introduced by (bisect log) [merge commit]:
commit 27d6e47f8e133167af51a3e39548cd3e9bed07da
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Mon Oct 14 05:07:36 2019 +0000

  Merge 5.4-rc3 into staging-next

Crash: WARNING in get_probe_ref (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
WARNING in get_probe_ref 0 (1) 2020/05/18 03:12
▶ ▼ Last patch testing requests (7)
Created Duration User Patch Repo Result
2023/09/02 16:42 14m retest repro upstream report log
2023/09/02 16:42 14m retest repro upstream report log
2023/06/22 11:20 13m retest repro upstream report log
2023/04/13 04:11 12m retest repro upstream report log
2023/01/11 20:32 22m retest repro upstream OK log
2022/10/12 10:30 19m retest repro upstream error OK
2022/10/03 17:30 18m retest repro upstream report log
▶ ▼ Fix bisection attempts (5)
Created Duration User Patch Repo Result
2020/11/07 06:09 16m bisect fix upstream error job log (0)
2020/10/08 04:08 33m bisect fix upstream job log (0) log
2020/09/01 16:41 33m bisect fix upstream job log (0) log
2020/08/02 08:54 33m bisect fix upstream job log (0) log
2020/06/13 04:34 32m (6) bisect fix upstream job log (0) log

Sample crash report:
RBP: 00007ffcd05f2de0 R08: 0000000000000002 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
 </TASK>
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4999 at kernel/trace/blktrace.c:1098 get_probe_ref+0x328/0x3e0 kernel/trace/blktrace.c:337
Modules linked in:
CPU: 1 PID: 4999 Comm: syz-executor156 Not tainted 6.4.0-rc7-syzkaller-00234-g547cc9be86f4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:blk_register_tracepoints kernel/trace/blktrace.c:1098 [inline]
RIP: 0010:get_probe_ref+0x328/0x3e0 kernel/trace/blktrace.c:337
Code: db 0f 85 c6 00 00 00 e8 d6 da f8 ff 48 c7 c7 00 91 f7 8c 5b e9 59 8a 26 09 e8 c4 da f8 ff 0f 0b e9 44 fd ff ff e8 b8 da f8 ff <0f> 0b e9 65 fd ff ff e8 ac da f8 ff 0f 0b e9 86 fd ff ff e8 a0 da
RSP: 0018:ffffc90003b3fb78 EFLAGS: 00010293
RAX: ffffffff8192aa38 RBX: 00000000fffffff4 RCX: ffff88802076d940
RDX: 0000000000000000 RSI: 00000000fffffff4 RDI: 0000000000000000
RBP: ffff88802d0f0800 R08: ffffffff8192a797 R09: fffff52000767f45
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11005a1e106
R13: dffffc0000000000 R14: ffff88802d0f0830 R15: ffff88802d0f0828
FS:  00005555557fb300(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbf87177284 CR3: 0000000029c15000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 do_blk_trace_setup+0x790/0x960 kernel/trace/blktrace.c:612
 __blk_trace_setup kernel/trace/blktrace.c:631 [inline]
 blk_trace_setup+0x119/0x1e0 kernel/trace/blktrace.c:649
 sg_ioctl_common drivers/scsi/sg.c:1117 [inline]
 sg_ioctl+0xa49/0x2e50 drivers/scsi/sg.c:1159
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbf8711f6a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 14 00 00 90 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcd05f2dc8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007fbf8711f6a9
RDX: 0000000020000040 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007ffcd05f2de0 R08: 0000000000000002 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/26 01:40 upstream 547cc9be86f4 09ffe269 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root WARNING in get_probe_ref
2022/06/25 16:37 upstream 6a0a17e6c6d1 a371c43c .config strace log report syz C ci-upstream-kasan-gce-smack-root WARNING in get_probe_ref
2020/05/14 03:47 upstream 24085f70a6e1 a885920d .config console log report syz C ci-upstream-kasan-gce
2022/02/06 12:44 upstream 90c9e950c0de a7dab638 .config console log report info ci-upstream-kasan-gce-smack-root WARNING in get_probe_ref
2020/05/14 03:03 upstream 24085f70a6e1 a885920d .config console log report ci-upstream-kasan-gce
* Struck through repros no longer work on HEAD.