public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8ecc009e206a956ab317@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] INFO: task hung in switchdev_deferred_process_work (2)
Date: Fri, 24 Mar 2023 19:29:27 -0700	[thread overview]
Message-ID: <00000000000060888105f7b047ce@google.com> (raw)
In-Reply-To: <20230325021143.1968-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFAIL: initialize_wifi_devices: failed set up IBSS network

2023/03/25 02:28:33 executed programs: 6
2023/03/25 02:28:33 result: hanged=false err=executor 0: 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 02:28:34 result: hanged=false err=executor 1: 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 02:28:34 result: hanged=false err=executor 2: 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 02:28:38 result: hanged=false err=executor 1: EOF
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)


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


2023/03/25 02:28:38 executed programs: 27


Tested on:

commit:         65aca32e Merge tag 'mm-hotfixes-stable-2023-03-24-17-0..
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=13227efec80000
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

Note: no patches were applied.

       reply	other threads:[~2023-03-25  2:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230325021143.1968-1-hdanton@sina.com>
2023-03-25  2:29 ` syzbot [this message]
     [not found] <20230325013831.1826-1-hdanton@sina.com>
2023-03-25  1:51 ` [syzbot] [wireless?] INFO: task hung in switchdev_deferred_process_work (2) syzbot
     [not found] <20230325011100.1765-1-hdanton@sina.com>
2023-03-25  1:24 ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00000000000060888105f7b047ce@google.com \
    --to=syzbot+8ecc009e206a956ab317@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox