panic: kernel diagnostic assertion "map->limit == rtmap_limit" f

5 views
Skip to first unread message

syzbot

unread,
Oct 20, 2024, 5:19:41 AM10/20/24
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: bcc47c46a274 Make ec EVP_PKEY_CTRL_MD handler match dsa/rs..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=16d12430580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=528d0ee59cf178132561

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f4b326ffb95f/disk-bcc47c46.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/e4260a4d8b0b/bsd-bcc47c46.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/11717604a4bd/kernel-bcc47c46.xz

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

panic: kernel diagnostic assertion "map->limit == rtmap_limit" f
ailed: file "/syzkaller/managers/main/kernel/sys/net/rtable.c",
line 131
Starting stack trace...
panic(ffffffff830b4120) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff83068a43,ffffffff83036f0c,83,ffffffff830a7417) at __assert+0x29
rtmap_grow(17,21) at rtmap_grow+0x1f3 sys/net/rtable.c:131
rtable_add(16) at rtable_add+0x279
if_createrdomain(16,ffff800000b10800) at if_createrdomain+0x40 sys/net/if.c:1945
ifioctl(fffffd8078b21820,8020699f,ffff80002a565cd0,ffff80002a5407c8) at ifioctl+0x19be sys/net/if.c:2294
sys_ioctl(ffff80002a5407c8,ffff80002a565eb0,ffff80002a565e00) at sys_ioctl+0x678
syscall(ffff80002a565eb0) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xbaf326447b0, 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

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jan 18, 2025, 4:19:21 AM1/18/25
to syzkaller-o...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages