[v6.1] SYZFAIL: writev failed (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 882efbdd9d34 Linux 6.1.155
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1795f92f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=92a68b89f302fb853b22
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cc4ea5e30f96/disk-882efbdd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a8e2e97ac897/vmlinux-882efbdd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c6b39d17aa12/bzImage-882efbdd.xz

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

SYZFAIL: writev failed
(errno 6: No such device or address)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=9 req=2103 state=1 status=9 (errno 11: Resource temporarily unavailable)


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