Hello,
syzbot found the following issue on:
HEAD commit: 61cfd264993d Revert "ipv4/fib: send notify when delete sou..
git tree: android13-5.15-lts
console output:
https://syzkaller.appspot.com/x/log.txt?x=160970c0e80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=86febd5cba631f80
dashboard link:
https://syzkaller.appspot.com/bug?extid=4956f9b851d6402719ab
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=13e4cd60e80000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=11dc9ecf680000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/12c3173d49c9/disk-61cfd264.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/aaf0b50ce030/vmlinux-61cfd264.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/d32e9000a96b/bzImage-61cfd264.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+4956f9...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at kernel/bpf/arraymap.c:1037!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 39 Comm: kworker/1:1 Not tainted 5.15.137-syzkaller-01792-g61cfd264993d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
Workqueue: events prog_array_map_clear_deferred
RIP: 0010:prog_array_map_poke_run+0x696/0x6b0 kernel/bpf/arraymap.c:1037
Code: 47 e6 ff 48 83 c4 70 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 bd 47 e6 ff 0f 0b e9 de f9 ff ff e8 b1 47 e6 ff 0f 0b e8 aa 47 e6 ff <0f> 0b e8 a3 47 e6 ff 0f 0b e8 9c 47 e6 ff 0f 0b 66 2e 0f 1f 84 00
RSP: 0018:ffffc9000028fb70 EFLAGS: 00010293
RAX: ffffffff8189af86 RBX: ffff8881159343d0 RCX: ffff8881069ba780
RDX: 0000000000000000 RSI: 00000000fffffff0 RDI: 00000000ffffffea
RBP: ffffc9000028fc08 R08: ffffffff8189ad11 R09: fffff52000051f39
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888120d04380
R13: dffffc0000000000 R14: ffff888115034c00 R15: 00000000fffffff0
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fae19370628 CR3: 00000001191ef000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
fd_array_map_delete_elem+0x154/0x250 kernel/bpf/arraymap.c:830
bpf_fd_array_map_clear kernel/bpf/arraymap.c:878 [inline]
prog_array_map_clear_deferred+0xf8/0x210 kernel/bpf/arraymap.c:1057
process_one_work+0x6bb/0xc10 kernel/workqueue.c:2317
worker_thread+0xad5/0x12a0 kernel/workqueue.c:2464
kthread+0x421/0x510 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Modules linked in:
---[ end trace ab3275692183dc20 ]---
RIP: 0010:prog_array_map_poke_run+0x696/0x6b0 kernel/bpf/arraymap.c:1037
Code: 47 e6 ff 48 83 c4 70 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 bd 47 e6 ff 0f 0b e9 de f9 ff ff e8 b1 47 e6 ff 0f 0b e8 aa 47 e6 ff <0f> 0b e8 a3 47 e6 ff 0f 0b e8 9c 47 e6 ff 0f 0b 66 2e 0f 1f 84 00
RSP: 0018:ffffc9000028fb70 EFLAGS: 00010293
RAX: ffffffff8189af86 RBX: ffff8881159343d0 RCX: ffff8881069ba780
RDX: 0000000000000000 RSI: 00000000fffffff0 RDI: 00000000ffffffea
RBP: ffffc9000028fc08 R08: ffffffff8189ad11 R09: fffff52000051f39
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888120d04380
R13: dffffc0000000000 R14: ffff888115034c00 R15: 00000000fffffff0
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fae192b3d58 CR3: 000000010c3dd000 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 report is already addressed, 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 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