From: syzbot <syzbot+5c3c53e6db862466e7b6@syzkaller.appspotmail.com>
To: chuck.lever@oracle.com, jlayton@kernel.org,
johannes.berg@intel.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, nbd@nbd.name,
syzkaller-bugs@googlegroups.com, toke@kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] possible deadlock in corrupted
Date: Sat, 23 Jul 2022 04:12:13 -0700 [thread overview]
Message-ID: <000000000000cdbe1105e4770541@google.com> (raw)
In-Reply-To: <000000000000cbe0e605e0caa8e0@google.com>
syzbot suspects this issue was fixed by commit:
commit f856373e2f31ffd340e47e2b00027bd4070f74b3
Author: Felix Fietkau <nbd@nbd.name>
Date: Tue May 31 19:08:24 2022 +0000
wifi: mac80211: do not wake queues on a vif that is being stopped
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11363672080000
start commit: 3abc3ae553c7 Merge tag '9p-for-5.19-rc4' of https://github..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=574cf8e4f636f8ff
dashboard link: https://syzkaller.appspot.com/bug?extid=5c3c53e6db862466e7b6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16545ce4080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1087453ff00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: wifi: mac80211: do not wake queues on a vif that is being stopped
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-07-23 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 17:18 [syzbot] possible deadlock in corrupted syzbot
2022-07-23 11:12 ` syzbot [this message]
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=000000000000cdbe1105e4770541@google.com \
--to=syzbot+5c3c53e6db862466e7b6@syzkaller.appspotmail.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=johannes.berg@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=syzkaller-bugs@googlegroups.com \
--cc=toke@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.