All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ededba317ddeca8b3f08@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, moonhee.lee.ca@gmail.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING in _ieee80211_sta_cur_vht_bw
Date: Tue, 01 Jul 2025 12:04:03 -0700	[thread overview]
Message-ID: <68643123.a70a0220.3b7e22.1f43.GAE@google.com> (raw)
In-Reply-To: <CAF3JpA5AaoPXnQ81PYoEP89kGbKype5Fcew8JWSds4xbz40s+g@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+ededba317ddeca8b3f08@syzkaller.appspotmail.com
Tested-by: syzbot+ededba317ddeca8b3f08@syzkaller.appspotmail.com

Tested on:

commit:         3f804361 Add linux-next specific files for 20250701
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=178c388c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=46111759e155f4cc
dashboard link: https://syzkaller.appspot.com/bug?extid=ededba317ddeca8b3f08
compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch:          https://syzkaller.appspot.com/x/patch.diff?x=108af88c580000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2025-07-01 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF3JpA5AaoPXnQ81PYoEP89kGbKype5Fcew8JWSds4xbz40s+g@mail.gmail.com>
2025-07-01 19:04 ` syzbot [this message]
2025-07-01 21:11 [PATCH] wifi: mac80211: reject opmode notification for unsupported channel widths Moon Hee Lee
2025-07-01 21:43 ` [syzbot] [wireless?] WARNING in _ieee80211_sta_cur_vht_bw syzbot
  -- strict thread matches above, loose matches on Subject: below --
2025-07-01 19:49 Moonhee Lee
2025-07-01 20:34 ` [syzbot] [wireless?] " syzbot
2025-06-26  5:52 syzbot
2025-06-26 12:57 ` syzbot

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=68643123.a70a0220.3b7e22.1f43.GAE@google.com \
    --to=syzbot+ededba317ddeca8b3f08@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moonhee.lee.ca@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 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.