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

4 views
Skip to first unread message

syzbot

unread,
May 9, 2025, 12:38:28 AM5/9/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ac7079a42ea5 Linux 6.1.137
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11ddc670580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b6c9ee6fabde22af
dashboard link: https://syzkaller.appspot.com/bug?extid=443e65ac0c7bfc1259db
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/235ed7912afd/disk-ac7079a4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/66591056046a/vmlinux-ac7079a4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/11e3c8def63d/bzImage-ac7079a4.xz

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

SYZFAIL: writev failed
(errno 6: No such device or address)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: ebtable checkpoint: socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)
(errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=1 req=52 state=3 status=67 (errno 9: Bad file descriptor)


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

unread,
Sep 29, 2025, 5:46:18 AM9/29/25
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages