panic: runtime error: floating point error [recovered]

Status: auto-obsoleted due to no activity on 2024/07/13 09:12
Reported-by: syzbot+37bd716fd69c893002e0@syzkaller.appspotmail.com
First crash: 841d, last: 841d
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-15 panic: runtime error: floating point error [recovered] (2) 2 1 859d 859d 0/2 auto-obsoleted due to no activity on 2024/06/25 05:19
android-6-1 panic: runtime error: floating point error [recovered] 2 3 855d 872d 0/2 auto-obsoleted due to no activity on 2024/06/29 09:32
upstream panic: runtime error: floating point error [recovered] 2 2 841d 857d 0/29 auto-obsoleted due to no activity on 2024/07/13 03:37
upstream panic: runtime error: floating point error [recovered] (2) 2 syz 1 508d 588d 0/29 upstream: reported syz repro on 2024/12/22 14:57
android-5-15 panic: runtime error: floating point error [recovered] 2 1 1327d 1327d 0/2 auto-obsoleted due to no activity on 2023/04/11 07:35

Sample crash report:
panic: runtime error: floating point error [recovered]
	panic: bytes.Buffer: too large
[signal SIGFPE: floating-point exception code=0x80 addr=0x0 pc=0x471c32]

goroutine 29 [Connection to 10.128.0.183 closed by remote host.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/14 09:07 android13-5.10-lts 4e1bc8d8e8ae c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 panic: runtime error: floating point error [recovered]
* Struck through repros no longer work on HEAD.