[v6.1] SYZFAIL: iptable checkpoint: socket(SOCK_STREAM, IPPROTO_TCP) failed

4 views
Skip to first unread message

syzbot

unread,
Nov 20, 2024, 10:57:32 PM11/20/24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b67dc5c9ade9 Linux 6.1.118
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=162cf6c0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d16b871b055cdb66
dashboard link: https://syzkaller.appspot.com/bug?extid=6cf85873595c20338d16
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0da3be0a4ab/disk-b67dc5c9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/08d2ee7b9438/vmlinux-b67dc5c9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/58a8b06ea421/bzImage-b67dc5c9.xz

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

SYZFAIL: iptable checkpoint: socket(SOCK_STREAM, IPPROTO_TCP) failed
family=10 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 1: Operation not permitted)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=4 req=5 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,
Apr 5, 2025, 9:08:17 AM4/5/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