[v5.15] SYZFAIL: read failed

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10fc9327980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d3fd5cca89ae935
dashboard link: https://syzkaller.appspot.com/bug?extid=a049a61c1dd1c2c7f106
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/1ca12b270c00/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4c4c618f8bc4/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e49c2df1f067/bzImage-3a592870.xz

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

SYZFAIL: read failed
(errno 4: Interrupted system call)
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=0 req=67 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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.