Hello,
syzbot found the following issue on:
HEAD commit: 50cbba13faa2 Linux 6.1.159
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16e0ab0a580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=31ea1cecaf34f0db
dashboard link:
https://syzkaller.appspot.com/bug?extid=8ee93674023b23375dab
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=127698ac580000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/7ad0bd66715a/disk-50cbba13.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/3284d626258e/vmlinux-50cbba13.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/a1f92ca7bbfc/Image-50cbba13.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+8ee936...@syzkaller.appspotmail.com
SYZFAIL: ioctl(HCISETSCAN) failed
(errno 22: Invalid argument)
loop exited with status 67
SYZFAIL: ioctl(HCIDEVUP) failed
(errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: ioctl(HCISETSCAN) failed
(errno 22: Invalid argument)
loop exited with status 67
SYZFAIL: writev failed
(errno 6: No such device or address)
loop exited with status 67
SYZFAIL: ioctl(HCIDEVUP) failed
(errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: ioctl(HCISETSCAN) failed
(errno 22: Invalid argument)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=1 (errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: ioctl(HCISETSCAN) failed
(errno 22: Invalid argument)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=1 (errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: ioctl(HCISETSCAN) failed
(errno 22: Invalid argument)
loop exited with status 67
SYZFAIL: writev failed
(errno 6: No such device or address)
loop exited with status 67
SYZFAIL: writev failed
(errno 6: No such device or address)
loop exited with status 67
SYZFAIL: ioctl(HCIDEVUP) failed
(errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: ioctl(HCISETSCAN) failed
(errno 22: Invalid argument)
loop exited with status 67
SYZFAIL: initialize_wifi_devices: failed set up IBSS network
device=0 (errno 132: Operation not possible due to RF-kill)
loop exited with status 67
SYZFAIL: repeatedly failed to execute the program
proc=4 req=21 state=3 status=67 (errno 32: Broken pipe)
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
---
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