From: syzbot <syzbot+9817a610349542589c42@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
emmanuel.grumbach@intel.com, gregory.greenman@intel.com,
jiri@nvidia.com, johannes.berg@intel.com,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING in ieee80211_link_release_channel
Date: Sun, 03 Dec 2023 09:12:07 -0800 [thread overview]
Message-ID: <000000000000ea98f3060b9e19c3@google.com> (raw)
In-Reply-To: <000000000000bcd80b06046a98ac@google.com>
syzbot suspects this issue was fixed by commit:
commit 88717def36f7b19f12d6ad6644e73bf91cf86375
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date: Wed Sep 13 11:56:51 2023 +0000
wifi: iwlwifi: mvm: add a debug print when we get a BAR
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=161d9230e80000
start commit: d68b4b6f307d Merge tag 'mm-nonmm-stable-2023-08-28-22-48' ..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c45ae22e154d76fa
dashboard link: https://syzkaller.appspot.com/bug?extid=9817a610349542589c42
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128eab18680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: wifi: iwlwifi: mvm: add a debug print when we get a BAR
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-12-03 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 1:48 [syzbot] [wireless?] WARNING in ieee80211_link_release_channel syzbot
2023-09-04 6:57 ` Johannes Berg
2023-11-07 8:25 ` syzbot
2023-12-03 17: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=000000000000ea98f3060b9e19c3@google.com \
--to=syzbot+9817a610349542589c42@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emmanuel.grumbach@intel.com \
--cc=gregory.greenman@intel.com \
--cc=jiri@nvidia.com \
--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=pabeni@redhat.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).