assert "map->limit == rtmap_limit" failed in rtable.c (2)

3 views

Skip to first unread message

syzbot

unread,

Feb 6, 2025, 1:09:25 PM2/6/25

to syzkaller-o...@googlegroups.com

Hello,

syzbot found the following issue on:

HEAD commit: 4a7e1005694f Update awk to the Jan 14, 2025 version. * Fi..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1093a4a4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=4b7aca0368015987c9cc

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/090fa20dffa9/disk-4a7e1005.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/aaa329f11a33/bsd-4a7e1005.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b9ed246eb46/kernel-4a7e1005.xz

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

panic: kernel diagnostic assertion "map->limit == rtmap_limit" failed: file "/syzkaller/managers/multicore/kernel/sys/net/rtable.c", line 131
Starting stack trace...
panic(ffffffff83151a97) at panic+0x1d0 sys/kern/subr_prf.c:229
__assert(ffffffff8310a2d9,ffffffff83046899,83,ffffffff83149df1) at __assert+0x29
rtable_init() at rtable_init
rtable_add(16) at rtable_add+0x2d9 rtable_alloc sys/net/rtable.c:373 [inline]
rtable_add(16) at rtable_add+0x2d9 sys/net/rtable.c:222
if_createrdomain(16,ffff800000b2c000) at if_createrdomain+0x40 sys/net/if.c:1946
ifioctl(ffff8000013e8708,8020699f,ffff80003c5a0d60,ffff80003b1931f8) at ifioctl+0x1a1e sys/net/if.c:2295
sys_ioctl(ffff80003b1931f8,ffff80003c5a0f40,ffff80003c5a0e90) at sys_ioctl+0x5c3
syscall(ffff80003c5a0f40) at syscall+0xbc6 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80003c5a0f40) at syscall+0xbc6 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x9fdfa2c3f90, count: 248
End of stack trace.

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