[moderation/CI] Re: Adding NO_STA flag and reworking RX link resolution

0 views
Skip to first unread message

syzbot ci

unread,
Feb 20, 2026, 10:21:03 AM (3 days ago) Feb 20
to syzkaller-upst...@googlegroups.com, syz...@lists.linux.dev
syzbot ci has tested the following series

[v1] Adding NO_STA flag and reworking RX link resolution
https://lore.kernel.org/all/20260220141929.2...@sipsolutions.net
* [RFC PATCH 1/8] wifi: iwlwifi: use link_sta internally to the driver
* [RFC PATCH 2/8] wifi: mac80211: change public RX API to use link stations
* [RFC PATCH 3/8] wifi: mac80211: refactor RX link_id and station handling
* [RFC PATCH 4/8] wifi: mac80211: rework RX packet handling
* [RFC PATCH 5/8] wifi: cfg80211: add attribute for TX/RX denoting there is no station
* [RFC PATCH 6/8] wifi: mac80211: report to cfg80211 when no STA is known for a frame
* [RFC PATCH 7/8] wifi: mac80211: pass station to ieee80211_tx_skb_tid
* [RFC PATCH 8/8] wifi: mac80211: pass error station if non-STA transmit was requested

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/aef950c6-dd02-4cc0-af4f-be3d1739f909

***

kernel build error

tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 8bf22c33e7a172fbc72464f4cc484d23a6b412ba
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/89235db4-5426-4ae6-95de-9d6c07b940e7/config

drivers/net/wireless/ath/ath11k/dp_rx.c:2503:28: error: incompatible pointer types passing 'struct ieee80211_sta *' to parameter of type 'struct ieee80211_link_sta *' [-Werror,-Wincompatible-pointer-types]

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syz...@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@googlegroups.com.

The email will later be sent to:
[benjam...@intel.com benj...@sipsolutions.net linux-w...@vger.kernel.org ramasamy....@oss.qualcomm.com rameshkuma...@oss.qualcomm.com]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid

Reply all
Reply to author
Forward
0 new messages