[v5.15] SYZFAIL: clone failed
0 views
Skip to first unread message
syzbot
Jan 28, 2024, 9:11:31 AMJan 28
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15817afde80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3292eb21c4b0adb2
dashboard link: https://syzkaller.appspot.com/bug?extid=5510c194bb4f61504724
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1459e64be80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/48c022810340/disk-6139f2a0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e0420b24130a/vmlinux-6139f2a0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ddfcb3eac737/bzImage-6139f2a0.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5510c1...@syzkaller.appspotmail.com
2024/01/28 13:35:02 [FATAL] executor failed 11 times: executor 2: exit status 67 err exit status 67
SYZFAIL: clone failed
(errno 11: Resource temporarily unavailable)
loop exited with status 67
exit status 67
SYZFAIL: clone failed
(errno 11: Resource temporarily unavailable)
loop exited with status 67
exit status 67
---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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 found the following issue on:
HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15817afde80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3292eb21c4b0adb2
dashboard link: https://syzkaller.appspot.com/bug?extid=5510c194bb4f61504724
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1459e64be80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/48c022810340/disk-6139f2a0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e0420b24130a/vmlinux-6139f2a0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ddfcb3eac737/bzImage-6139f2a0.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5510c1...@syzkaller.appspotmail.com
2024/01/28 13:35:02 [FATAL] executor failed 11 times: executor 2: exit status 67 err exit status 67
SYZFAIL: clone failed
(errno 11: Resource temporarily unavailable)
loop exited with status 67
exit status 67
SYZFAIL: clone failed
(errno 11: Resource temporarily unavailable)
loop exited with status 67
exit status 67
---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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
Jan 28, 2024, 9:22:27 AMJan 28
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 883d1a956208 Linux 6.1.75
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=126a51a0180000
kernel config: https://syzkaller.appspot.com/x/.config?x=e191632f30d1d52a
dashboard link: https://syzkaller.appspot.com/bug?extid=9ab144302e8a3af6a0b7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1673b6bbe80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0213a1024e59/disk-883d1a95.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4196bd2137f2/vmlinux-883d1a95.xz
kernel image: https://storage.googleapis.com/syzbot-assets/945849d03d1a/bzImage-883d1a95.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
2024/01/28 13:44:19 [FATAL] executor failed 11 times: executor 4: exit status 67 err exit status 67
Reply all
Reply to author
Forward
0 new messages