syzbot


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: 1435d, last: 37d
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 (4)
Title Replies (including bot) Last reply
[syzbot] Monthly block report (Mar 2024) 0 (1) 2024/03/12 09:29
[syzbot] Monthly trace report (Jan 2024) 0 (1) 2024/01/26 21:55
[syzbot] Monthly trace report (Nov 2023) 0 (1) 2023/11/23 13:12
WARNING in get_probe_ref 0 (1) 2020/05/18 03:12
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/03/12 16:00 29m retest repro upstream report log
2024/01/23 10:08 43m retest repro upstream report log
2024/01/23 10:08 53m retest repro upstream report log
2023/11/11 18:58 22m retest repro upstream report log
2023/11/11 18:58 13m retest repro upstream report log
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
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:
WARNING: CPU: 1 PID: 5149 at kernel/trace/blktrace.c:1096 blk_register_tracepoints kernel/trace/blktrace.c:1096 [inline]
WARNING: CPU: 1 PID: 5149 at kernel/trace/blktrace.c:1096 get_probe_ref+0x31d/0x400 kernel/trace/blktrace.c:337
Modules linked in:
CPU: 1 PID: 5149 Comm: syz-executor278 Not tainted 6.8.0-rc6-syzkaller-00011-g45ec2f5f6ed3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:blk_register_tracepoints kernel/trace/blktrace.c:1096 [inline]
RIP: 0010:get_probe_ref+0x31d/0x400 kernel/trace/blktrace.c:337
Code: c3 31 ff 89 c6 e8 e3 60 f8 ff 85 db 0f 85 e4 00 00 00 e8 96 5c f8 ff 48 c7 c7 00 51 18 8e 5b e9 59 aa d5 09 e8 84 5c f8 ff 90 <0f> 0b 90 e9 42 fd ff ff e8 76 5c f8 ff 90 0f 0b 90 e9 61 fd ff ff
RSP: 0018:ffffc900043c7b58 EFLAGS: 00010293
RAX: ffffffff819b10cc RBX: 00000000fffffff4 RCX: ffff888076119dc0
RDX: 0000000000000000 RSI: 00000000fffffff4 RDI: 0000000000000000
RBP: ffff88801e23dd10 R08: ffffffff819b0e0a R09: 1ffff92000878f40
R10: dffffc0000000000 R11: fffff52000878f41 R12: 1ffff11003c47ba8
R13: dffffc0000000000 R14: ffff88801e23dd40 R15: ffff88801e23dd38
FS:  00007fa83097f6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa83060b0bb CR3: 00000000201e0000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 do_blk_trace_setup+0x790/0x970 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:1118 [inline]
 sg_ioctl+0xa4c/0x2e80 drivers/scsi/sg.c:1160
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:871 [inline]
 __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:857
 do_syscall_64+0xf9/0x240
 entry_SYSCALL_64_after_hwframe+0x6f/0x77
RIP: 0033:0x7fa830648119
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 1b 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa83097f208 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fa8306f0028 RCX: 00007fa830648119
RDX: 0000000020000000 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007fa8306f0020 R08: 00007fa83097efa6 R09: 0000000000003434
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fa83097f210
R13: 0000000000000002 R14: 00007fa83069b012 R15: 2367732f7665642f
 </TASK>

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/27 13:09 upstream 45ec2f5f6ed3 05e69c83 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce WARNING in get_probe_ref
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
2024/02/27 11:29 upstream 45ec2f5f6ed3 05e69c83 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce WARNING in get_probe_ref
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.