WARNING in blk_register_tracepoints
14 views
Skip to first unread message
syzbot
Feb 7, 2022, 7:21:19 AM2/7/22
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=164f89b4700000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=a0e23bb3193f983f6a0d
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1274d584700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1146e662700000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a0e23b...@syzkaller.appspotmail.com
RDX: 0000000020000140 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007ffc007bb6d0 R08: 0000000000000002 R09: 00007ffc007bb6b8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ffc007bb6ba R14: 00007fe62cf5b4b0 R15: 000000000000000c
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8100 at kernel/trace/blktrace.c:1172 blk_register_tracepoints.cold+0xe9/0x180 kernel/trace/blktrace.c:1172
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 8100 Comm: syz-executor408 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:blk_register_tracepoints.cold+0xe9/0x180 kernel/trace/blktrace.c:1172
Code: f9 e8 61 39 6e f9 48 c7 c7 a0 c5 6e 88 e8 c0 6a ff ff 0f 0b e9 74 a1 73 f9 e8 49 39 6e f9 48 c7 c7 a0 c5 6e 88 e8 a8 6a ff ff <0f> 0b e9 2f a1 73 f9 e8 31 39 6e f9 48 c7 c7 a0 c5 6e 88 e8 90 6a
RSP: 0018:ffff8880b164fa70 EFLAGS: 00010286
RAX: 0000000000000024 RBX: 00000000fffffff4 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10162c9f40
RBP: ffff8880a335d600 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 00000000fffffff0
R13: 0000000000000000 R14: ffff8880a335d630 R15: 0000000000000000
get_probe_ref kernel/trace/blktrace.c:328 [inline]
do_blk_trace_setup+0x915/0xb40 kernel/trace/blktrace.c:590
__blk_trace_setup+0xca/0x180 kernel/trace/blktrace.c:609
blk_trace_setup+0x43/0x60 kernel/trace/blktrace.c:627
sg_ioctl+0x270/0x2720 drivers/scsi/sg.c:1121
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fe62cee61c9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 15 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:00007ffc007bb688 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007fe62cee61c9
RDX: 0000000020000140 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007ffc007bb6d0 R08: 0000000000000002 R09: 00007ffc007bb6b8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ffc007bb6ba R14: 00007fe62cf5b4b0 R15: 000000000000000c
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=164f89b4700000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=a0e23bb3193f983f6a0d
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1274d584700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1146e662700000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a0e23b...@syzkaller.appspotmail.com
RDX: 0000000020000140 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007ffc007bb6d0 R08: 0000000000000002 R09: 00007ffc007bb6b8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ffc007bb6ba R14: 00007fe62cf5b4b0 R15: 000000000000000c
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8100 at kernel/trace/blktrace.c:1172 blk_register_tracepoints.cold+0xe9/0x180 kernel/trace/blktrace.c:1172
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 8100 Comm: syz-executor408 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:blk_register_tracepoints.cold+0xe9/0x180 kernel/trace/blktrace.c:1172
Code: f9 e8 61 39 6e f9 48 c7 c7 a0 c5 6e 88 e8 c0 6a ff ff 0f 0b e9 74 a1 73 f9 e8 49 39 6e f9 48 c7 c7 a0 c5 6e 88 e8 a8 6a ff ff <0f> 0b e9 2f a1 73 f9 e8 31 39 6e f9 48 c7 c7 a0 c5 6e 88 e8 90 6a
RSP: 0018:ffff8880b164fa70 EFLAGS: 00010286
RAX: 0000000000000024 RBX: 00000000fffffff4 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10162c9f40
RBP: ffff8880a335d600 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 00000000fffffff0
R13: 0000000000000000 R14: ffff8880a335d630 R15: 0000000000000000
get_probe_ref kernel/trace/blktrace.c:328 [inline]
do_blk_trace_setup+0x915/0xb40 kernel/trace/blktrace.c:590
__blk_trace_setup+0xca/0x180 kernel/trace/blktrace.c:609
blk_trace_setup+0x43/0x60 kernel/trace/blktrace.c:627
sg_ioctl+0x270/0x2720 drivers/scsi/sg.c:1121
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fe62cee61c9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 15 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:00007ffc007bb688 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007fe62cee61c9
RDX: 0000000020000140 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007ffc007bb6d0 R08: 0000000000000002 R09: 00007ffc007bb6b8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ffc007bb6ba R14: 00007fe62cf5b4b0 R15: 000000000000000c
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
syzbot
Feb 15, 2022, 2:12:19 PM2/15/22
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 8034e99d1a01 Linux 4.14.266
syzbot found the following issue on:
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11648ec4700000
kernel config: https://syzkaller.appspot.com/x/.config?x=647e517ce784ab05
dashboard link: https://syzkaller.appspot.com/bug?extid=514adb58c01526c423a9
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15889674700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=113b9f8c700000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
RDX: 0000000020000140 RSI: 00000000c0481273 RDI: 0000000000000003
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7977 at kernel/trace/blktrace.c:1192 blk_register_tracepoints+0x28a/0x2f0 kernel/trace/blktrace.c:1192
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 7977 Comm: syz-executor647 Not tainted 4.14.266-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
Call Trace:
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:blk_register_tracepoints+0x28a/0x2f0 kernel/trace/blktrace.c:1192
RSP: 0018:ffff88809de4fb20 EFLAGS: 00010297
RAX: ffff8880b45f02c0 RBX: ffff8880ac6f6780 RCX: fffffbfff17d9ba8
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000286
RBP: ffff8880b3cddd80 R08: ffff8880b45f02c0 R09: dffffc0000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000fffffff0
R13: ffff8880b3cdddb0 R14: 0000000000000000 R15: 0000000000000000
get_probe_ref kernel/trace/blktrace.c:340 [inline]
do_blk_trace_setup+0x8a1/0xac0 kernel/trace/blktrace.c:602
__blk_trace_setup+0xa3/0x120 kernel/trace/blktrace.c:621
blk_trace_setup+0x43/0x60 kernel/trace/blktrace.c:639
sg_ioctl+0x232/0x2620 drivers/scsi/sg.c:1131
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7efd9e5fbcd9
RSP: 002b:00007ffffa4c1b88 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007efd9e5fbcd9
RDX: 0000000020000140 RSI: 00000000c0481273 RDI: 0000000000000003
RBP: 00007ffffa4c1b90 R08: 0000000000000002 R09: 00007efd9e003533
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Reply all
Reply to author
Forward
0 new messages