mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+34463a129786910405dd@syzkaller.appspotmail.com>
To: clang-built-linux@googlegroups.com, davem@davemloft.net,
	 johannes.berg@intel.com, johannes@sipsolutions.net,
	kuba@kernel.org,  kvalo@codeaurora.org,
	linux-kernel@vger.kernel.org,  linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org,  ramonreisfontes@gmail.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING in __rate_control_send_low (3)
Date: Tue, 29 Oct 2024 13:32:02 -0700	[thread overview]
Message-ID: <67214642.050a0220.4735a.0262.GAE@google.com> (raw)
In-Reply-To: <671cedcb.050a0220.2b8c0f.01b1.GAE@google.com>

syzbot has bisected this issue to:

commit 119aadf816f5373dc82ca4109d6d5b777e00475b
Author: Ramon Fontes <ramonreisfontes@gmail.com>
Date:   Fri May 15 16:46:40 2020 +0000

    mac80211_hwsim: report the WIPHY_FLAG_SUPPORTS_5_10_MHZ capability

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=170e3687980000
start commit:   b5abbf612092 Merge branch 'mptcp-sched-fix-some-lock-issues'
git tree:       net
final oops:     https://syzkaller.appspot.com/x/report.txt?x=148e3687980000
console output: https://syzkaller.appspot.com/x/log.txt?x=108e3687980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=309bb816d40abc28
dashboard link: https://syzkaller.appspot.com/bug?extid=34463a129786910405dd
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17a76ebb980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17f0ee40580000

Reported-by: syzbot+34463a129786910405dd@syzkaller.appspotmail.com
Fixes: 119aadf816f5 ("mac80211_hwsim: report the WIPHY_FLAG_SUPPORTS_5_10_MHZ capability")

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

      parent reply	other threads:[~2024-10-29 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 13:25 syzbot
2024-10-29  3:17 ` syzbot
2024-10-29 20:32 ` 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=67214642.050a0220.4735a.0262.GAE@google.com \
    --to=syzbot+34463a129786910405dd@syzkaller.appspotmail.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=davem@davemloft.net \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ramonreisfontes@gmail.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
all inboxes | Powered by JetHome®