[Android 6.1] invalid opcode in bpf_dispatcher_xdp

0 views
Skip to first unread message

syzbot

unread,
May 28, 2023, 8:21:59 AM5/28/23
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 500484f5be02 BACKPORT: FROMGIT: Multi-gen LRU: fix working..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=1607e5c1280000
kernel config: https://syzkaller.appspot.com/x/.config?x=772a621c45fe488b
dashboard link: https://syzkaller.appspot.com/bug?extid=bbeac345f0dc2a3d110a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150d2869280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13220d1e280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e2dc880692ed/disk-500484f5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/36fb8cf6ec84/vmlinux-500484f5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c7510e94b236/bzImage-500484f5.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bbeac3...@syzkaller.appspotmail.com

invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 494 Comm: syz-executor265 Not tainted 6.1.25-syzkaller-00305-g500484f5be02 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:bpf_dispatcher_xdp+0x1d/0x1000
Code: cc cc cc cc cc cc cc cc cc cc cc cc cc 48 81 fa 50 20 00 a0 7f 47 48 81 fa 10 20 00 a0 7f 2e 48 81 fa 5c 09 00 a0 7f 15 48 81 <fa> 5c 09 00 a0 0f 84 f4 cd ff ff ff e2 66 0f 1f 44 00 00 48 81 fa
RSP: 0018:ffffc900014b78b0 EFLAGS: 00010246
RAX: ffffffff8406fab7 RBX: ffffc900014b7c00 RCX: ffff88810fa726e4
RDX: ffffffffa0002010 RSI: ffffc90000919048 RDI: ffffc900014b7c00
RBP: ffffc900014b78d0 R08: ffffffff8420135d R09: ffffed1021f4e4c1
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffffc90000919030 R14: ffffffffa0002010 R15: ffffc90000919048
FS: 00005555571663c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007facd84d8130 CR3: 0000000121087000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__bpf_prog_run include/linux/filter.h:600 [inline]
bpf_prog_run_xdp include/linux/filter.h:775 [inline]
bpf_test_run+0x470/0xa40 net/bpf/test_run.c:400
bpf_prog_test_run_xdp+0x7a7/0x1130 net/bpf/test_run.c:1389
bpf_prog_test_run+0x3b0/0x630 kernel/bpf/syscall.c:3630
__sys_bpf+0x59f/0x7f0 kernel/bpf/syscall.c:4985
__do_sys_bpf kernel/bpf/syscall.c:5071 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5069 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5069
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7facd8467d69
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:00007ffc96bd2f88 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007ffc96bd2fc0 RCX: 00007facd8467d69
RDX: 0000000000000048 RSI: 0000000020000000 RDI: 000000000000000a
RBP: 0000000000000000 R08: 0000000000028543 R09: 0000000000028543
R10: 00007ffc96bd2a10 R11: 0000000000000246 R12: 00000000000f4240
R13: 0000000000028543 R14: 00007ffc96bd2fac R15: 00007ffc96bd2fb0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:bpf_dispatcher_xdp+0x1d/0x1000
Code: cc cc cc cc cc cc cc cc cc cc cc cc cc 48 81 fa 60 22 00 a0 7f 47 48 81 fa 10 20 00 a0 7f 2e 48 81 fa 5c 09 00 a0 7f 15 48 81 <fa> 5c 09 00 a0 0f 84 f4 cd ff ff ff e2 66 0f 1f 44 00 00 48 81 fa
RSP: 0018:ffffc900014b78b0 EFLAGS: 00010246
RAX: ffffffff8406fab7 RBX: ffffc900014b7c00 RCX: ffff88810fa726e4
RDX: ffffffffa0002010 RSI: ffffc90000919048 RDI: ffffc900014b7c00
RBP: ffffc900014b78d0 R08: ffffffff8420135d R09: ffffed1021f4e4c1
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffffc90000919030 R14: ffffffffa0002010 R15: ffffc90000919048
FS: 00005555571663c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007facd84db1d0 CR3: 0000000121087000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages