linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: syzbot <syzbot+8dd98a9e98ee28dc484a@syzkaller.appspotmail.com>,
	"clang-built-linux@googlegroups.com"
	<clang-built-linux@googlegroups.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"johannes.berg@intel.com" <johannes.berg@intel.com>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"nathan@kernel.org" <nathan@kernel.org>,
	"ndesaulniers@google.com" <ndesaulniers@google.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"syzkaller-bugs@googlegroups.com"
	<syzkaller-bugs@googlegroups.com>
Subject: RE: [syzbot] [wireless?] WARNING in __rate_control_send_low (2)
Date: Fri, 26 Jul 2024 03:26:47 +0000	[thread overview]
Message-ID: <c06f8308cc84412a93b81418aaa32fa8@realtek.com> (raw)
In-Reply-To: <00000000000011de5f061dd387f0@google.com>

<syzbot+8dd98a9e98ee28dc484a@syzkaller.appspotmail.com> wrote:
> syzbot has bisected this issue to:
> 
> commit 9df66d5b9f45c39b3925d16e8947cc10009b186d
> Author: Ping-Ke Shih <pkshih@realtek.com>
> Date:   Wed Jun 9 07:59:44 2021 +0000
> 
>     cfg80211: fix default HE tx bitrate mask in 2G band
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13e233fd980000
> start commit:   51835949dda3 Merge tag 'net-next-6.11' of git://git.kernel..
> git tree:       net-next
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=101233fd980000
> console output: https://syzkaller.appspot.com/x/log.txt?x=17e233fd980000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=d3bdd09ea2371c89
> dashboard link: https://syzkaller.appspot.com/bug?extid=8dd98a9e98ee28dc484a
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14608749980000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=178b9195980000
> 
> Reported-by: syzbot+8dd98a9e98ee28dc484a@syzkaller.appspotmail.com
> Fixes: 9df66d5b9f45 ("cfg80211: fix default HE tx bitrate mask in 2G band")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

I sent a patch [1] to avoid the warning of

   no supported rates for sta (null) (0xffffffff, band 0) in rate_mask 0x0 with flags 0x0

[1] https://lore.kernel.org/linux-wireless/20240726031520.7616-1-pkshih@realtek.com/T/#u


      reply	other threads:[~2024-07-26  3:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  7:46 [syzbot] [wireless?] WARNING in __rate_control_send_low (2) syzbot
2024-05-25 22:11 ` syzbot
2024-07-18 17:29 ` syzbot
2024-07-22 10:30 ` syzbot
2024-07-26  3:26   ` Ping-Ke Shih [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=c06f8308cc84412a93b81418aaa32fa8@realtek.com \
    --to=pkshih@realtek.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.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=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+8dd98a9e98ee28dc484a@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).