All of lore.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 18:24:38 -0700	[thread overview]
Message-ID: <000000000000929ce705f7af5fde@google.com> (raw)
In-Reply-To: <20230325011100.1765-1-hdanton@sina.com>

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


       reply	other threads:[~2023-03-25  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230325011100.1765-1-hdanton@sina.com>
2023-03-25  1:24 ` 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] <20230325021143.1968-1-hdanton@sina.com>
2023-03-25  2:29 ` 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=000000000000929ce705f7af5fde@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.