All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d805aca692aded25f888@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
	johannes.berg@intel.com,  johannes@sipsolutions.net,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	 linux-wireless@vger.kernel.org, m.lobanov@rosa.ru,
	netdev@vger.kernel.org,  pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING in minstrel_ht_update_caps
Date: Thu, 08 May 2025 08:49:03 -0700	[thread overview]
Message-ID: <681cd26f.050a0220.a19a9.0116.GAE@google.com> (raw)
In-Reply-To: <00000000000054bc390618ccb092@google.com>

syzbot suspects this issue was fixed by commit:

commit 16ee3ea8faef8ff042acc15867a6c458c573de61
Author: Mikhail Lobanov <m.lobanov@rosa.ru>
Date:   Mon Mar 17 10:31:37 2025 +0000

    wifi: mac80211: check basic rates validity in sta_link_apply_parameters

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=101444f4580000
start commit:   0ec986ed7bab tcp: fix incorrect undo caused by DSACK of TL..
git tree:       net
kernel config:  https://syzkaller.appspot.com/x/.config?x=864caee5f78cab51
dashboard link: https://syzkaller.appspot.com/bug?extid=d805aca692aded25f888
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12fb56e1980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17490685980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: wifi: mac80211: check basic rates validity in sta_link_apply_parameters

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

      parent reply	other threads:[~2025-05-08 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19 11:14 [syzbot] [wireless?] WARNING in minstrel_ht_update_caps syzbot
2024-05-19 11:55 ` syzbot
2025-05-08 15:49 ` 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=681cd26f.050a0220.a19a9.0116.GAE@google.com \
    --to=syzbot+d805aca692aded25f888@syzkaller.appspotmail.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=m.lobanov@rosa.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.