linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+96ff6cfc4551fcc29342@syzkaller.appspotmail.com>
To: allison@lohutok.net, andrew@lunn.ch, aviad.krawczyk@huawei.com,
	axboe@kernel.dk, davem@davemloft.net, gregkh@linuxfoundation.org,
	hdanton@sina.com, io-uring@vger.kernel.org,
	johannes.berg@intel.com, johannes@sipsolutions.net,
	kuba@kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	linyunsheng@huawei.com, luobin9@huawei.com,
	netdev@vger.kernel.org, pabeni@redhat.com, phind.uet@gmail.com,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	viro@zeniv.linux.org.uk, xiaoguang.wang@linux.alibaba.com
Subject: Re: [syzbot] INFO: task hung in linkwatch_event (2)
Date: Tue, 05 Apr 2022 00:38:06 -0700	[thread overview]
Message-ID: <0000000000006574b705dbe3533f@google.com> (raw)
In-Reply-To: <0000000000001779fd05a46b001f@google.com>

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=1048725f700000
start commit:   dd86e7fa07a3 Merge tag 'pci-v5.11-fixes-2' of git://git.ke..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=e83e68d0a6aba5f6
dashboard link: https://syzkaller.appspot.com/bug?extid=96ff6cfc4551fcc29342
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11847bc4d00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1267e5a0d00000

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

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2022-04-05  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  9:59 INFO: task hung in linkwatch_event (2) syzbot
2020-05-06  1:38 ` Yunsheng Lin
     [not found] ` <20200506042533.13044-1-hdanton@sina.com>
2020-05-06 11:20   ` Yunsheng Lin
2020-12-11  2:25 ` syzbot
2022-04-05  7:38 ` syzbot [this message]
2022-05-12 13:26   ` [syzbot] " Dmitry Vyukov

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=0000000000006574b705dbe3533f@google.com \
    --to=syzbot+96ff6cfc4551fcc29342@syzkaller.appspotmail.com \
    --cc=allison@lohutok.net \
    --cc=andrew@lunn.ch \
    --cc=aviad.krawczyk@huawei.com \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdanton@sina.com \
    --cc=io-uring@vger.kernel.org \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linyunsheng@huawei.com \
    --cc=luobin9@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=phind.uet@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xiaoguang.wang@linux.alibaba.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).