From: syzbot <syzbot+c54ded83396afee31eb1@syzkaller.appspotmail.com>
To: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in blk_register_tracepoints
Date: Mon, 07 Feb 2022 21:40:30 -0800 [thread overview]
Message-ID: <000000000000ae0f7b05d77b27b5@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d8ad2ce873ab Merge tag 'ext4_for_linus_stable' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15665db2700000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee3797346aa03884
dashboard link: https://syzkaller.appspot.com/bug?extid=c54ded83396afee31eb1
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e00d84700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119fd0c2700000
Bisection is inconclusive: the issue happens on the oldest tested release.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=171a984fb00000
final oops: https://syzkaller.appspot.com/x/report.txt?x=149a984fb00000
console output: https://syzkaller.appspot.com/x/log.txt?x=109a984fb00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c54ded83396afee31eb1@syzkaller.appspotmail.com
RBP: 00007ffc2d88d100 R08: 0000000000000002 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
</TASK>
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3595 at kernel/trace/blktrace.c:1090 blk_register_tracepoints+0x2dc/0x3a0 kernel/trace/blktrace.c:1090
Modules linked in:
CPU: 0 PID: 3595 Comm: syz-executor147 Not tainted 5.17.0-rc2-syzkaller-00398-gd8ad2ce873ab #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:blk_register_tracepoints+0x2dc/0x3a0 kernel/trace/blktrace.c:1090
Code: 48 c7 c7 00 3d 82 8d e8 f2 69 fb ff 31 ff 89 c3 89 c6 e8 e7 a8 f9 ff 85 db 0f 85 ba 00 00 00 5b e9 b9 a6 f9 ff e8 b4 a6 f9 ff <0f> 0b e9 4b fd ff ff e8 a8 a6 f9 ff 0f 0b e9 6c fd ff ff e8 9c a6
RSP: 0018:ffffc9000279fbc0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 00000000fffffff4 RCX: 0000000000000000
RDX: ffff888023011d00 RSI: ffffffff817ed1dc RDI: 0000000000000003
RBP: ffff8881469d4300 R08: 0000000000000000 R09: ffffc9000279fa67
R10: ffffffff817ecf26 R11: 0000000000000000 R12: ffffc9000279fc70
R13: ffff8881469d4328 R14: ffff8881470196d0 R15: ffff8881469d4330
FS: 0000555556142300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc2d88d0c8 CR3: 00000000715ef000 CR4: 0000000000350ee0
Call Trace:
<TASK>
get_probe_ref kernel/trace/blktrace.c:326 [inline]
do_blk_trace_setup+0x9c3/0xc80 kernel/trace/blktrace.c:570
__blk_trace_setup+0xca/0x180 kernel/trace/blktrace.c:589
blk_trace_setup+0x43/0x60 kernel/trace/blktrace.c:607
sg_ioctl_common drivers/scsi/sg.c:1123 [inline]
sg_ioctl+0x257/0x2780 drivers/scsi/sg.c:1165
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__x64_sys_ioctl+0x193/0x200 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f7e080026d9
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:00007ffc2d88d0e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f7e080026d9
RDX: 0000000020000140 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007ffc2d88d100 R08: 0000000000000002 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2022-02-08 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 5:40 syzbot [this message]
2023-07-07 22:32 ` [syzbot] [block?] [trace?] WARNING in blk_register_tracepoints syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000ae0f7b05d77b27b5@google.com \
--to=syzbot+c54ded83396afee31eb1@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.