linux-kernel - Re: [syzbot] [wireless?] INFO: task hung in switchdev_deferred_process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <000000000000929ce705f7af5fde@google.com>
Date:   Fri, 24 Mar 2023 18:24:38 -0700
From:   syzbot <syzbot+8ecc009e206a956ab317@...kaller.appspotmail.com>
To:     hdanton@...a.com, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [wireless?] INFO: task hung in switchdev_deferred_process_work
 (2)

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFAIL: wrong response packet

2023/03/25 01:23:02 result: hanged=false err=executor 1: EOF
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)


2023/03/25 01:23:02 result: hanged=false err=executor 2: EOF
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)


2023/03/25 01:23:05 result: hanged=false err=executor 1: EOF
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)


2023/03/25 01:23:05 executed programs: 8
2023/03/25 01:23:07 result: hanged=false err=executor 4: exit 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
2023/03/25 01:23:07 result: hanged=false err=executor 3: failed to write control pipe: write |1: broken pipe

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
2023/03/25 01:23:07 result: hanged=false err=executor 5: failed to write control pipe: write |1: broken pipe

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
2023/03/25 01:23:10 result: hanged=false err=executor 4: EOF
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)


2023/03/25 01:23:11 result: hanged=false err=executor 2: exit 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
2023/03/25 01:23:11 executed programs: 21
2023/03/25 01:23:11 result: hanged=false err=executor 5: EOF
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)


2023/03/25 01:23:11 result: hanged=false err=executor 3: EOF
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)




Tested on:

commit:         e76db6e5 Merge tag 'arm-fixes-6.3-2' of git://git.kern..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=13ac8d0ec80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4a2ca2de6ed94982
dashboard link: https://syzkaller.appspot.com/bug?extid=8ecc009e206a956ab317
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1169ef75c80000