[v5.15] SYZFAIL: failed to recv rpc (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3dea0e7f549e Linux 5.15.186
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=103b2a8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=644ffcb58c0b09d3
dashboard link: https://syzkaller.appspot.com/bug?extid=86d34fda2e8f09577b42
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3d73d6f07b0c/disk-3dea0e7f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4064de18c9e9/vmlinux-3dea0e7f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/069c7b1e74a9/bzImage-3dea0e7f.xz

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

SYZFAIL: failed to recv rpc
fd=3 want=4 recv=0 n=-1 (errno 104: Connection reset by peer)


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