From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+00ce7332120071df39b1@syzkaller.appspotmail.com>
Cc: arunkumar@space-mep.com, davem@davemloft.net,
johannes.berg@intel.com, johannes@sipsolutions.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
phind.uet@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in ieee80211_chanctx_num_assigned
Date: Thu, 12 May 2022 15:20:19 +0200 [thread overview]
Message-ID: <CACT4Y+ZqX84gCjcxtsRSan4Rf8C26rH5xQ7LfwnNHOqx0fDFjA@mail.gmail.com> (raw)
In-Reply-To: <000000000000c86f9d05d57b594d@google.com>
On Thu, 13 Jan 2022 at 20:04, syzbot
<syzbot+00ce7332120071df39b1@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 563fbefed46ae4c1f70cffb8eb54c02df480b2c2
> Author: Nguyen Dinh Phi <phind.uet@gmail.com>
> Date: Wed Oct 27 17:37:22 2021 +0000
>
> cfg80211: call cfg80211_stop_ap when switch from P2P_GO type
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16afe84bb00000
> start commit: 7f75285ca572 Merge tag 'for-5.12/dm-fixes-3' of git://git...
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=b5591c832f889fd9
> dashboard link: https://syzkaller.appspot.com/bug?extid=00ce7332120071df39b1
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1393cbf9d00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1238ba29d00000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: cfg80211: call cfg80211_stop_ap when switch from P2P_GO type
Looks legit:
#syz fix: cfg80211: call cfg80211_stop_ap when switch from P2P_GO type
prev parent reply other threads:[~2022-05-12 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 12:45 general protection fault in ieee80211_chanctx_num_assigned syzbot
2020-11-22 13:56 ` syzbot
2022-01-13 19:04 ` [syzbot] " syzbot
2022-05-12 13:20 ` Dmitry Vyukov [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=CACT4Y+ZqX84gCjcxtsRSan4Rf8C26rH5xQ7LfwnNHOqx0fDFjA@mail.gmail.com \
--to=dvyukov@google.com \
--cc=arunkumar@space-mep.com \
--cc=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=phind.uet@gmail.com \
--cc=syzbot+00ce7332120071df39b1@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).