[moderation] [bpf?] BUG: corrupted list in bpf_lru_push_free

1 view
Skip to first unread message

syzbot

unread,
May 24, 2024, 10:23:21 PMMay 24
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6e51b4b5bbc0 Merge tag 'mips_6.10' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16f04d92980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d5d254b2919253a
dashboard link: https://syzkaller.appspot.com/bug?extid=8967cc86e5b4f6b1c33a
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
CC: [and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net edd...@gmail.com hao...@google.com john.fa...@gmail.com jo...@kernel.org kps...@kernel.org linux-...@vger.kernel.org marti...@linux.dev s...@google.com so...@kernel.org yongho...@linux.dev]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-6e51b4b5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4a78abf5bef3/vmlinux-6e51b4b5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/283fe971fc00/bzImage-6e51b4b5.xz

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

list_del corruption. next->prev should be ffffc9002baebab8, but was ffffc9002baebab9. (next=ffffe8ffab5072c0)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:65!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 3 PID: 13794 Comm: syz-executor.1 Not tainted 6.9.0-syzkaller-09868-g6e51b4b5bbc0 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:__list_del_entry_valid_or_report+0x141/0x1c0 lib/list_debug.c:65
Code: eb fc 90 0f 0b 48 89 c2 48 c7 c7 c0 8f 8f 8b e8 e5 43 eb fc 90 0f 0b 48 89 d1 48 c7 c7 40 90 8f 8b 48 89 c2 e8 d0 43 eb fc 90 <0f> 0b 48 89 34 24 e8 f4 db 67 fd 48 8b 34 24 e9 d5 fe ff ff 48 89
RSP: 0018:ffffc9000d26f9a8 EFLAGS: 00010086
RAX: 000000000000006d RBX: ffffc9002baebab8 RCX: ffffffff816f3549
RDX: 0000000000000000 RSI: ffffffff816fc0c6 RDI: 0000000000000005
RBP: ffff888012daf2c0 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000002 R12: ffffe8ffab5072b0
R13: ffffc9002baebaca R14: 0000000000000004 R15: ffffe8ffab5072d8
FS: 0000000000000000(0000) GS:ffff88802c300000(0063) knlGS:00000000f5e5bb40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000056ef6480 CR3: 0000000025906000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry_valid include/linux/list.h:124 [inline]
__list_del_entry include/linux/list.h:215 [inline]
list_move include/linux/list.h:298 [inline]
bpf_common_lru_push_free kernel/bpf/bpf_lru_list.c:531 [inline]
bpf_lru_push_free+0x311/0x5e0 kernel/bpf/bpf_lru_list.c:561
htab_lru_push_free kernel/bpf/hashtab.c:1197 [inline]
__htab_map_lookup_and_delete_batch+0x174b/0x2820 kernel/bpf/hashtab.c:1870
bpf_map_do_batch+0x32a/0x6e0 kernel/bpf/syscall.c:5198
__sys_bpf+0x52e0/0x5830 kernel/bpf/syscall.c:5747
__do_sys_bpf kernel/bpf/syscall.c:5794 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5792 [inline]
__ia32_sys_bpf+0x76/0xe0 kernel/bpf/syscall.c:5792
do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]
__do_fast_syscall_32+0x75/0x120 arch/x86/entry/common.c:386
do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411
entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf7269579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000f5e5b5ac EFLAGS: 00000292 ORIG_RAX: 0000000000000165
RAX: ffffffffffffffda RBX: 0000000000000019 RCX: 0000000020000800
RDX: 0000000000000038 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0x141/0x1c0 lib/list_debug.c:65
Code: eb fc 90 0f 0b 48 89 c2 48 c7 c7 c0 8f 8f 8b e8 e5 43 eb fc 90 0f 0b 48 89 d1 48 c7 c7 40 90 8f 8b 48 89 c2 e8 d0 43 eb fc 90 <0f> 0b 48 89 34 24 e8 f4 db 67 fd 48 8b 34 24 e9 d5 fe ff ff 48 89
RSP: 0018:ffffc9000d26f9a8 EFLAGS: 00010086
RAX: 000000000000006d RBX: ffffc9002baebab8 RCX: ffffffff816f3549
RDX: 0000000000000000 RSI: ffffffff816fc0c6 RDI: 0000000000000005
RBP: ffff888012daf2c0 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000002 R12: ffffe8ffab5072b0
R13: ffffc9002baebaca R14: 0000000000000004 R15: ffffe8ffab5072d8
FS: 0000000000000000(0000) GS:ffff88802c300000(0063) knlGS:00000000f5e5bb40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000056ef6480 CR3: 0000000025906000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 2 bytes skipped:
0: 10 06 adc %al,(%rsi)
2: 03 74 b4 01 add 0x1(%rsp,%rsi,4),%esi
6: 10 07 adc %al,(%rdi)
8: 03 74 b0 01 add 0x1(%rax,%rsi,4),%esi
c: 10 08 adc %cl,(%rax)
e: 03 74 d8 01 add 0x1(%rax,%rbx,8),%esi
1e: 00 51 52 add %dl,0x52(%rcx)
21: 55 push %rbp
22: 89 e5 mov %esp,%ebp
24: 0f 34 sysenter
26: cd 80 int $0x80
* 28: 5d pop %rbp <-- trapping instruction
29: 5a pop %rdx
2a: 59 pop %rcx
2b: c3 ret
2c: 90 nop
2d: 90 nop
2e: 90 nop
2f: 90 nop
30: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi


---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

If the report is a duplicate of another one, 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