panic: runtime error: floating point error

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0ed90f62b184 UPSTREAM: ALSA: pcm: Move rwsem lock inside s..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=13b0d6c1480000
kernel config: https://syzkaller.appspot.com/x/.config?x=8dc6bbfc90d8f09a
dashboard link: https://syzkaller.appspot.com/bug?extid=55dff8071a101f291217
compiler: Debian clang version 13.0.1-6~deb11u1, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148f1649480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dd9b08fe9f06/disk-0ed90f62.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4aa53427ed99/vmlinux-0ed90f62.xz
kernel image: https://storage.googleapis.com/syzbot-assets/58f56e9f6727/bzImage-0ed90f62.xz

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

panic: runtime error: floating point error
[signal SIGFPE: floating-point exception code=0x80 addr=0x0 pc=0x46e1e0]

goroutine 9 [running]:
sync.(*Mutex).Unlock(0x9621c0)
/usr/local/go/src/sync/mutex.go:179
github.com/google/syzkaller/pkg/ipc.(*Gate).Leave(0xc00034c100, 0x4)
/syzkaller/gopath/src/github.com/google/syzkaller/pkg/ipc/gate.go:75 +0xc8
main.(*Context).execute(0xc00051c000, 0x2, 0x0, 0x0)
/syzkaller/gopath/src/github.com/google/syzkaller/tools/syz-execprog/execprog.go:198 +0x458
main.(*Context).run(0xc00051c000, 0x0)
/syzkaller/gopath/src/github.com/google/syzkaller/tools/syz-execprog/execprog.go:157 +0xed
main.main.func3()
/syzkaller/gopath/src/github.com/google/syzkaller/tools/syz-execprog/execprog.go:120 +0x5c
created by main.main
/syzkaller/gopath/src/github.com/google/syzkaller/tools/syz-execprog/execprog.go:118 +0x61c
[


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches