SYZFAIL: SIGFPE (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b3de60980210 style: Recomend SPDX licenses
git tree: freebsd-src
console output: https://syzkaller.appspot.com/x/log.txt?x=11ce7fdf980000
dashboard link: https://syzkaller.appspot.com/bug?extid=e7d4f1d9b86a4c931669

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

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

SYZFAIL: SIGFPE
pid 768 (syz-executor), jid 0, uid 0: exited on signal 8 (no core dump - too large)
Connection to 10.128.0.68 closed by remote host.
pid 763 (sshd), jid 0, uid 0: exited on signal 8 (no core dump - bad address)
pid 737 (sleep), jid 0, uid 0: exited on signal 8 (no core dump - other error)
pid 682 (sshd), jid 0, uid 0: exited on signal 8 (no core dump - bad address)
2025-02-25T13:33:38.540168+00:00 ci-freebsd-main-2.us-central1-b.c.syzkaller.internal init 1077 - - fatal signal: Floating point exception
2025-02-25T13:33:38.548136+00:00 ci-freebsd-main-2.us-central1-b.c.syzkaller.internal init 1076 - - fatal signal: Floating point exception
2025-02-25T13:33:38.618254+00:00 ci-freebsd-main-2.us-central1-b.c.syzkaller.internal init 1075 - - fatal signal: Floating point exception
pid 1001 (dhclient), jid 0, uid 0: exited on signal 8 (core dumped)
pid 1072 (syz-executor), tap0: tun/tap protocol violation, non-controlling process closed last.
ifaddr cache = 0xfffffe00585f8900 is deleted
tap0: link state changed to DOWN
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c800
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c800
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c800
pid 1073 (syz-executor), jid 0, uid 0: exited on signal 8 (no core dump - bad address)
pid 1073 (syz-executor), tap2: tun/tap protocol violation, non-controlling process closed last.
ifaddr cache = 0xfffffe00585f8780 is deleted
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c000
tap2: link state changed to DOWN
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c000
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c000
pid 973 (sh), jid 0, uid 0: exited on signal 8 (core dumped)
pid 765 (csh), jid 0, uid 0: exited on signal 8 (core dumped)
pid 996 (dhclient), jid 0, uid 0: exited on signal 8 (core dumped)
pid 1083 (getty), jid 0, uid 0: exited on signal 8 (core dumped)
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3b800
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3b800
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3b800
pid 1081 (getty), jid 0, uid 0: exited on signal 8 (core dumped)
pid 1079 (getty), jid 0, uid 0: exited on signal 8 (core dumped)
if_delmulti_locked: detaching ifnet instance 0xfffffe00547e2800
if_delmulti_locked: detaching ifnet instance 0xfffffe00547e2800
if_delmulti_locked: detaching ifnet instance 0xfffffe00547e2800
pid 1080 (getty), jid 0, uid 0: exited on signal 8 (core dumped)
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c000
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c000
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c000
pid 1082 (getty), jid 0, uid 0: exited on signal 8 (core dumped)
pid 1078 (getty), jid 0, uid 0: exited on signal 8 (core dumped)
pid 1074 (syz-executor), jid 0, uid 0: exited on signal 8 (core dumped)
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c800
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c800
if_delmulti_locked: detaching ifnet instance 0xfffffe0058d3c800


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.