All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8b512026a7ec10dcbdd9@syzkaller.appspotmail.com>
To: johannes.berg@intel.com, johannes@sipsolutions.net,
	 linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] WARNING in sta_info_insert_rcu (4)
Date: Mon, 16 Jun 2025 08:45:02 -0700	[thread overview]
Message-ID: <68503bfe.050a0220.4562c.0008.GAE@google.com> (raw)
In-Reply-To: <20250616171838.7433379cab5d.I47444d63c72a0bd58d2e2b67bb99e1fea37eec6f@changeid>

Hello,

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

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

Tested on:

commit:         e04c78d8 Linux 6.16-rc2
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13f5ee82580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8f72e140c622500d
dashboard link: https://syzkaller.appspot.com/bug?extid=8b512026a7ec10dcbdd9
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=14ae15d4580000

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

  reply	other threads:[~2025-06-16 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 15:18 [PATCH wireless v2] wifi: mac80211: drop invalid source address OCB frames Johannes Berg
2025-06-16 15:45 ` syzbot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-16 13:40 [PATCH] " Johannes Berg
2025-06-16 14:02 ` [syzbot] [wireless?] WARNING in sta_info_insert_rcu (4) syzbot
2024-11-18 16:56 syzbot
2025-01-16  9:35 ` 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=68503bfe.050a0220.4562c.0008.GAE@google.com \
    --to=syzbot+8b512026a7ec10dcbdd9@syzkaller.appspotmail.com \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --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.