AI Trajectory


Trajectory: (Expand/Collapse All)
Seq Timestamp Type Name Duration
0/0 2026/09/16 00:08 flow patch-triage
0m Args:
null

Results:
{
  "EnableConfigs": null,
  "FocusSymbols": [],
  "KMSANReasoning": "",
  "NeedsKMSAN": false,
  "Reasoning": "The patch only updates documentation/web URLs in the MAINTAINERS file and does not modify any executable kernel code.",
  "WorthFuzzing": false
}

1/1 2026/09/16 00:08 action read-patch-diff
0m Args:
null

Results:
{
  "PatchDiff": "commit 688e423c68e9c8b56939fcea12e13331ba2950d1\nAuthor: syz-cluster \u003ctriage@syzkaller.com\u003e\nDate:   Wed Sep 16 00:08:33 2026 +0000\n\n    syz-cluster: applied patch under review\n\ndiff --git a/MAINTAINERS b/MAINTAINERS\nindex b23fb6f2f4ef4..f6ead73ab92db 100644\n--- a/MAINTAINERS\n+++ b/MAINTAINERS\n@@ -113,7 +113,7 @@ F:\tnet/6lowpan/\n M:\tJohannes Berg \u003cjohannes@sipsolutions.net\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tMaintained\n-W:\thttps://wireless.wiki.kernel.org/\n+W:\thttps://wireless.docs.kernel.org/en/latest/\n Q:\thttps://patchwork.kernel.org/project/linux-wireless/list/\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git\n@@ -4260,13 +4260,13 @@ M:\tNick Kossifidis \u003cmickflemm@gmail.com\u003e\n M:\tLuis Chamberlain \u003cmcgrof@kernel.org\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tMaintained\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/ath5k\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/ath5k.html\n F:\tdrivers/net/wireless/ath/ath5k/\n \n ATHEROS ATH6KL WIRELESS DRIVER\n L:\tlinux-wireless@vger.kernel.org\n S:\tOrphan\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/ath6kl\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/ath6kl.html\n F:\tdrivers/net/wireless/ath/ath6kl/\n \n ATI_REMOTE2 DRIVER\n@@ -4535,14 +4535,14 @@ B43 WIRELESS DRIVER\n L:\tlinux-wireless@vger.kernel.org\n L:\tb43-dev@lists.infradead.org\n S:\tOrphan\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/b43\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/b43.html\n F:\tdrivers/net/wireless/broadcom/b43/\n \n B43LEGACY WIRELESS DRIVER\n L:\tlinux-wireless@vger.kernel.org\n L:\tb43-dev@lists.infradead.org\n S:\tOrphan\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/b43\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/b43.html\n F:\tdrivers/net/wireless/broadcom/b43legacy/\n \n BACKLIGHT CLASS/SUBSYSTEM\n@@ -5919,7 +5919,7 @@ CARL9170 LINUX COMMUNITY WIRELESS DRIVER\n M:\tChristian Lamparter \u003cchunkeey@googlemail.com\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tMaintained\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/carl9170\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/carl9170.html\n F:\tdrivers/net/wireless/ath/carl9170/\n \n CAVIUM I2C DRIVER\n@@ -13560,7 +13560,7 @@ INTEL WIRELESS WIFI LINK (iwlwifi)\n M:\tMiri Korenblit \u003cmiriam.rachel.korenblit@intel.com\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tSupported\n-W:\thttps://wireless.wiki.kernel.org/en/users/drivers/iwlwifi\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi.html\n T:\tgit https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git/\n F:\tdrivers/net/wireless/intel/iwlwifi/\n \n@@ -15661,7 +15661,7 @@ MAC80211\n M:\tJohannes Berg \u003cjohannes@sipsolutions.net\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tMaintained\n-W:\thttps://wireless.wiki.kernel.org/\n+W:\thttps://wireless.docs.kernel.org/en/latest/\n Q:\thttps://patchwork.kernel.org/project/linux-wireless/list/\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git\n@@ -18920,7 +18920,7 @@ NETWORKING DRIVERS (WIRELESS)\n M:\tJohannes Berg \u003cjohannes@sipsolutions.net\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tMaintained\n-W:\thttps://wireless.wiki.kernel.org/\n+W:\thttps://wireless.docs.kernel.org/en/latest/\n Q:\thttps://patchwork.kernel.org/project/linux-wireless/list/\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git\n@@ -20592,7 +20592,7 @@ P54 WIRELESS DRIVER\n M:\tChristian Lamparter \u003cchunkeey@googlemail.com\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tMaintained\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/p54\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/p54.html\n F:\tDocumentation/devicetree/bindings/net/wireless/st,stlc4560.yaml\n F:\tdrivers/net/wireless/intersil/\n \n@@ -22282,7 +22282,7 @@ M:\tJeff Johnson \u003cjjohnson@kernel.org\u003e\n L:\tlinux-wireless@vger.kernel.org\n L:\tath12k@lists.infradead.org\n S:\tSupported\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/ath12k\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/ath12k.html\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git\n F:\tdrivers/net/wireless/ath/ath12k/\n N:\tath12k\n@@ -22292,7 +22292,7 @@ M:\tJeff Johnson \u003cjjohnson@kernel.org\u003e\n L:\tlinux-wireless@vger.kernel.org\n L:\tath10k@lists.infradead.org\n S:\tSupported\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/ath10k\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/ath10k.html\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git\n F:\tdrivers/net/wireless/ath/ath10k/\n N:\tath10k\n@@ -22302,8 +22302,8 @@ M:\tJeff Johnson \u003cjjohnson@kernel.org\u003e\n L:\tlinux-wireless@vger.kernel.org\n L:\tath11k@lists.infradead.org\n S:\tSupported\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/ath11k\n-B:\thttps://wireless.wiki.kernel.org/en/users/Drivers/ath11k/bugreport\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/ath11k.html\n+B:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/ath11k/bugreport.html\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git\n F:\tdrivers/net/wireless/ath/ath11k/\n N:\tath11k\n@@ -22312,7 +22312,7 @@ QUALCOMM ATHEROS ATH9K WIRELESS DRIVER\n M:\tToke Høiland-Jørgensen \u003ctoke@toke.dk\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tMaintained\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/ath9k\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/ath9k.html\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git\n F:\tDocumentation/devicetree/bindings/net/wireless/qca,ath9k.yaml\n F:\tdrivers/net/wireless/ath/ath9k/\n@@ -22654,7 +22654,7 @@ M:\tLoic Poulain \u003cloic.poulain@oss.qualcomm.com\u003e\n L:\twcn36xx@lists.infradead.org\n L:\tlinux-wireless@vger.kernel.org\n S:\tSupported\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/wcn36xx\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/wcn36xx.html\n F:\tdrivers/net/wireless/ath/wcn36xx/\n \n QUANTENNA QTNFMAC WIRELESS DRIVER\n@@ -23413,7 +23413,7 @@ RFKILL\n M:\tJohannes Berg \u003cjohannes@sipsolutions.net\u003e\n L:\tlinux-wireless@vger.kernel.org\n S:\tMaintained\n-W:\thttps://wireless.wiki.kernel.org/\n+W:\thttps://wireless.docs.kernel.org/en/latest/\n Q:\thttps://patchwork.kernel.org/project/linux-wireless/list/\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git\n T:\tgit git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git\n@@ -27508,8 +27508,8 @@ F:\tdrivers/media/platform/ti/vpe/\n TI WILINK WIRELESS DRIVERS\n L:\tlinux-wireless@vger.kernel.org\n S:\tOrphan\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/wl12xx\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/wl1251\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/wl12xx.html\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/wl1251.html\n F:\tdrivers/net/wireless/ti/\n \n TIMEKEEPING, CLOCKSOURCE CORE, NTP, ALARMTIMER\n@@ -29386,7 +29386,7 @@ F:\tdrivers/hid/hid-wiimote*\n WILOCITY WIL6210 WIRELESS DRIVER\n L:\tlinux-wireless@vger.kernel.org\n S:\tOrphan\n-W:\thttps://wireless.wiki.kernel.org/en/users/Drivers/wil6210\n+W:\thttps://wireless.docs.kernel.org/en/latest/en/users/drivers/wil6210.html\n F:\tdrivers/net/wireless/ath/wil6210/\n \n WINBOND CIR DRIVER\n"
}

2/1 2026/09/16 00:08 agent patch-evaluator
0m Model:
core

Args:
null

Results:
{
  "EnableConfigs": null,
  "FocusSymbols": [],
  "Reasoning": "The patch only updates documentation/web URLs in the MAINTAINERS file and does not modify any executable kernel code.",
  "WorthFuzzing": false
}

Instruction:
You are an expert Linux kernel maintainer and security engineer.
Your job is to review a provided patch series and evaluate whether it warrants fuzzing with syzkaller.

IMPORTANT: The changes have ALREADY been applied and committed as the HEAD commit in
your workspace. Do NOT rely on internal assumptions. You must actively use your code access
tools to inspect the actual source code, callers, and surrounding context.

================================================================================
1. CORE TRIAGE PHILOSOPHY
================================================================================
The goal of patch fuzzing is to discover crashes, regressions, exposed latent bugs,
and newly triggered assertions introduced by the patch series.

- REACHABILITY IS THE PRIMARY GATE:
  Fuzzing can only discover bugs in code that can actually execute in standard virtualized
  environments (GCE or QEMU, utilizing software-emulated devices like USB gadgets, netdev, tun/tap).
  If the modified code is structurally unreachable (see Section 2), it MUST NOT be fuzzed,
  regardless of whether it adds assertions or complex logic.

- DO NOT BLINDLY TRUST "NO FUNCTIONAL CHANGE" (NFCI) OR "REFACTORING" CLAIMS:
  Patch authors routinely label changes as "cleanups", "refactorings", or state
  "No functional change intended". Do NOT take these claims at face value.
  Code refactorings that rearrange logic, introduce helper functions, or alter state management
  in core subsystems frequently introduce subtle semantic shifts or uncover latent kernel bugs.
  If reachable executable code is modified or refactored, it MUST be fuzzed.

- NEW OR MODIFIED ASSERTIONS IN REACHABLE CODE MUST BE FUZZED:
  When a patch introduces or modifies runtime checks or assertions (e.g., WARN_ON*, VM_WARN_ON*,
  BUG_ON*, lockdep_assert*) in reachable code paths, it enforces new or stricter invariants.
  Even if the author believes the invariant always holds, fuzzing is essential to verify whether
  an unusual sequence of operations can violate it.

================================================================================
2. WHEN TO RETURN WorthFuzzing=false (NEGATIVE CRITERIA)
================================================================================
Return WorthFuzzing=false ONLY IF all modified code falls strictly into one or more of these categories:

- Non-kernel and non-executable changes:
  * Modifications to Documentation/, comments, or spelling fixes.
  * User-space directories, self-tests, samples, or scripts (e.g., tools/, samples/, scripts/, usr/)
    that do not affect the compiled kernel image (vmlinux) or kernel modules.
  * Purely decorative logging (e.g., message strings in pr_err, printk, dev_info) or tracepoints
    that do not alter control flow or data structures.
  * Build system or Kconfig changes that do not alter compiled C logic.
- Structurally unreachable hardware:
  * Vendor-specific PCIe switches, SmartNICs, or GPU drivers (e.g., mlxsw, pds_core, qed,
    ionic, amdgpu) requiring physical ASIC/PCIe cards not emulated in standard QEMU.
- Unreachable execution paths:
  * Driver teardown callbacks (.remove, .shutdown, pci_unregister_driver) executed only during
    physical PCI hot-unplug or manual sysfs driver unbinding.
  * Code paths exclusive to architectures other than the target architecture.

================================================================================
3. WHEN TO RETURN WorthFuzzing=true (POSITIVE CRITERIA)
================================================================================
Return WorthFuzzing=true whenever the patch touches reachable executable code, including:
- Core Subsystems:
  * Any logic modifications in memory management (mm/), synchronization/locking (kernel/locking/),
    BPF, scheduler, core networking, VFS, or syscall handling.
- Refactorings and Code Cleanups:
  * Any restructuring of reachable data structures, helper abstractions, or algorithm flows.
- Runtime Assertions and Defensive Checks:
  * Any introduction or alteration of assertions (WARN_ON*, VM_WARN_ON*, BUG_ON*, etc.) in reachable paths.
- Reachable Drivers and Protocols:
  * Drivers accessible via virtual buses (virtio, USB gadget, loopback, netlink, binder, sockets, etc.).

================================================================================
4. EXTRACTING FocusSymbols (PREVENTING DILUTION)
================================================================================
When WorthFuzzing=true, you must extract specific kernel functions into FocusSymbols to guide the fuzzer:

- AVOID UBIQUITOUS LIFECYCLE HOT-PATHS:
  Do NOT list generic, ubiquitous functions called by almost every program in the corpus
  (including, but not limited to: general memory allocators and deallocators, page fault
  and trap handlers, or core synchronization primitives; this is not an exhaustive list).
  Listing ubiquitous functions causes the fuzzer to classify thousands of unrelated tests as "focused",
  which severely dilutes fuzzing effort away from the actual changes.

- TARGET SPECIFIC FEATURE LOGIC AND ENTRYPOINTS:
  List functions that specifically implement the logic being added or altered, or direct API entrypoints
  for the subsystem feature under review.

- HANDLING STATIC INLINE FUNCTIONS IN HEADERS (.h):
  Compiler-inlined static functions (such as static inlines in mm/*.h or include/linux/*.h) lack
  distinct symbol addresses in vmlinux and cannot be targeted directly by symbol coverage filters.
  If the changes are primarily in static inline helpers, identify non-static, feature-specific caller
  functions in .c files that exercise them (avoiding ubiquitous lifecycle wrappers).

================================================================================
5. IDENTIFYING EnableConfigs
================================================================================
Identify any specific CONFIG_ options required to properly compile and reach the modified code:
- Inspect Kconfig files and #ifdef guards; do not make assumptions.
- Check "depends on" lines in Kconfig to include any non-standard parent subsystem configs needed.
- Strip any 'CONFIG_' prefix (e.g., return "NET_IPV4" instead of "CONFIG_NET_IPV4").
Prefer calling several tools at the same time to save round-trips.


Use set-results tool to provide results of the analysis.
It must be called exactly once before the final reply.
Ignore results of this tool.

Prompt:
Target architecture: amd64

For your convenience, here is the diff of the changes:
commit 688e423c68e9c8b56939fcea12e13331ba2950d1
Author: syz-cluster <triage@syzkaller.com>
Date:   Wed Sep 16 00:08:33 2026 +0000

    syz-cluster: applied patch under review

diff --git a/MAINTAINERS b/MAINTAINERS
index b23fb6f2f4ef4..f6ead73ab92db 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -113,7 +113,7 @@ F:	net/6lowpan/
 M:	Johannes Berg <johannes@sipsolutions.net>
 L:	linux-wireless@vger.kernel.org
 S:	Maintained
-W:	https://wireless.wiki.kernel.org/
+W:	https://wireless.docs.kernel.org/en/latest/
 Q:	https://patchwork.kernel.org/project/linux-wireless/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
@@ -4260,13 +4260,13 @@ M:	Nick Kossifidis <mickflemm@gmail.com>
 M:	Luis Chamberlain <mcgrof@kernel.org>
 L:	linux-wireless@vger.kernel.org
 S:	Maintained
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/ath5k
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath5k.html
 F:	drivers/net/wireless/ath/ath5k/
 
 ATHEROS ATH6KL WIRELESS DRIVER
 L:	linux-wireless@vger.kernel.org
 S:	Orphan
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/ath6kl
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath6kl.html
 F:	drivers/net/wireless/ath/ath6kl/
 
 ATI_REMOTE2 DRIVER
@@ -4535,14 +4535,14 @@ B43 WIRELESS DRIVER
 L:	linux-wireless@vger.kernel.org
 L:	b43-dev@lists.infradead.org
 S:	Orphan
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/b43
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/b43.html
 F:	drivers/net/wireless/broadcom/b43/
 
 B43LEGACY WIRELESS DRIVER
 L:	linux-wireless@vger.kernel.org
 L:	b43-dev@lists.infradead.org
 S:	Orphan
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/b43
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/b43.html
 F:	drivers/net/wireless/broadcom/b43legacy/
 
 BACKLIGHT CLASS/SUBSYSTEM
@@ -5919,7 +5919,7 @@ CARL9170 LINUX COMMUNITY WIRELESS DRIVER
 M:	Christian Lamparter <chunkeey@googlemail.com>
 L:	linux-wireless@vger.kernel.org
 S:	Maintained
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/carl9170
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/carl9170.html
 F:	drivers/net/wireless/ath/carl9170/
 
 CAVIUM I2C DRIVER
@@ -13560,7 +13560,7 @@ INTEL WIRELESS WIFI LINK (iwlwifi)
 M:	Miri Korenblit <miriam.rachel.korenblit@intel.com>
 L:	linux-wireless@vger.kernel.org
 S:	Supported
-W:	https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi.html
 T:	git https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git/
 F:	drivers/net/wireless/intel/iwlwifi/
 
@@ -15661,7 +15661,7 @@ MAC80211
 M:	Johannes Berg <johannes@sipsolutions.net>
 L:	linux-wireless@vger.kernel.org
 S:	Maintained
-W:	https://wireless.wiki.kernel.org/
+W:	https://wireless.docs.kernel.org/en/latest/
 Q:	https://patchwork.kernel.org/project/linux-wireless/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
@@ -18920,7 +18920,7 @@ NETWORKING DRIVERS (WIRELESS)
 M:	Johannes Berg <johannes@sipsolutions.net>
 L:	linux-wireless@vger.kernel.org
 S:	Maintained
-W:	https://wireless.wiki.kernel.org/
+W:	https://wireless.docs.kernel.org/en/latest/
 Q:	https://patchwork.kernel.org/project/linux-wireless/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
@@ -20592,7 +20592,7 @@ P54 WIRELESS DRIVER
 M:	Christian Lamparter <chunkeey@googlemail.com>
 L:	linux-wireless@vger.kernel.org
 S:	Maintained
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/p54
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/p54.html
 F:	Documentation/devicetree/bindings/net/wireless/st,stlc4560.yaml
 F:	drivers/net/wireless/intersil/
 
@@ -22282,7 +22282,7 @@ M:	Jeff Johnson <jjohnson@kernel.org>
 L:	linux-wireless@vger.kernel.org
 L:	ath12k@lists.infradead.org
 S:	Supported
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/ath12k
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath12k.html
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git
 F:	drivers/net/wireless/ath/ath12k/
 N:	ath12k
@@ -22292,7 +22292,7 @@ M:	Jeff Johnson <jjohnson@kernel.org>
 L:	linux-wireless@vger.kernel.org
 L:	ath10k@lists.infradead.org
 S:	Supported
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/ath10k
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath10k.html
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git
 F:	drivers/net/wireless/ath/ath10k/
 N:	ath10k
@@ -22302,8 +22302,8 @@ M:	Jeff Johnson <jjohnson@kernel.org>
 L:	linux-wireless@vger.kernel.org
 L:	ath11k@lists.infradead.org
 S:	Supported
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/ath11k
-B:	https://wireless.wiki.kernel.org/en/users/Drivers/ath11k/bugreport
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath11k.html
+B:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath11k/bugreport.html
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git
 F:	drivers/net/wireless/ath/ath11k/
 N:	ath11k
@@ -22312,7 +22312,7 @@ QUALCOMM ATHEROS ATH9K WIRELESS DRIVER
 M:	Toke Høiland-Jørgensen <toke@toke.dk>
 L:	linux-wireless@vger.kernel.org
 S:	Maintained
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/ath9k
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath9k.html
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git
 F:	Documentation/devicetree/bindings/net/wireless/qca,ath9k.yaml
 F:	drivers/net/wireless/ath/ath9k/
@@ -22654,7 +22654,7 @@ M:	Loic Poulain <loic.poulain@oss.qualcomm.com>
 L:	wcn36xx@lists.infradead.org
 L:	linux-wireless@vger.kernel.org
 S:	Supported
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/wcn36xx
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/wcn36xx.html
 F:	drivers/net/wireless/ath/wcn36xx/
 
 QUANTENNA QTNFMAC WIRELESS DRIVER
@@ -23413,7 +23413,7 @@ RFKILL
 M:	Johannes Berg <johannes@sipsolutions.net>
 L:	linux-wireless@vger.kernel.org
 S:	Maintained
-W:	https://wireless.wiki.kernel.org/
+W:	https://wireless.docs.kernel.org/en/latest/
 Q:	https://patchwork.kernel.org/project/linux-wireless/list/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
@@ -27508,8 +27508,8 @@ F:	drivers/media/platform/ti/vpe/
 TI WILINK WIRELESS DRIVERS
 L:	linux-wireless@vger.kernel.org
 S:	Orphan
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/wl12xx
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/wl1251
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/wl12xx.html
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/wl1251.html
 F:	drivers/net/wireless/ti/
 
 TIMEKEEPING, CLOCKSOURCE CORE, NTP, ALARMTIMER
@@ -29386,7 +29386,7 @@ F:	drivers/hid/hid-wiimote*
 WILOCITY WIL6210 WIRELESS DRIVER
 L:	linux-wireless@vger.kernel.org
 S:	Orphan
-W:	https://wireless.wiki.kernel.org/en/users/Drivers/wil6210
+W:	https://wireless.docs.kernel.org/en/latest/en/users/drivers/wil6210.html
 F:	drivers/net/wireless/ath/wil6210/
 
 WINBOND CIR DRIVER

3/2 2026/09/16 00:08 llm patch-evaluator
0m Model:
gemini-3.8-flash

Args:
null

Results:
null

Tokens:
							input: 5754
							output: 54
							thoughts: 316
						

Thoughts:
**My Assessment of the Patch**

Okay, so this patch is a straightforward one. It's just a diff to the `MAINTAINERS` file, changing those old `wireless.wiki.kernel.org` URLs to the new `wireless.docs.kernel.org` ones. Let's see... I've got my ruleset in my head for whether this warrants fuzzing or not, so let me quickly run through the criteria.

The key question is, does this fall under those negative criteria? Let me see… "Non-kernel and non-executable changes, like documentation updates". *Ding! Ding! Ding!* `MAINTAINERS` is purely documentation; metadata really. It’s non-executable. It's not C code that's compiled into the kernel image or any module. It's not altering any control flow or data structures, nor is it affecting any build logic. It's just a metadata file. This clearly qualifies as a negative case for fuzzing.

Therefore: `WorthFuzzing` is `false`. Since this is a documentation change, there aren’t any interesting symbols to focus on or any kernel configs to enable for fuzzing. Thus, `FocusSymbols` and `EnableConfigs` are both empty lists. My reasoning is solid: the patch solely updates documentation URLs in the `MAINTAINERS` file, which is irrelevant to any executable kernel code, and thus does not warrant fuzzing.

Okay, just to be extra sure, I'll go ahead and call set-results.



4/2 2026/09/16 00:08 tool set-results
0m Args:
{
  "EnableConfigs": [],
  "FocusSymbols": [],
  "Reasoning": "The patch only updates documentation/web URLs in the MAINTAINERS file and does not modify any executable kernel code.",
  "WorthFuzzing": false
}

Results:
{
  "EnableConfigs": null,
  "FocusSymbols": [],
  "Reasoning": "The patch only updates documentation/web URLs in the MAINTAINERS file and does not modify any executable kernel code.",
  "WorthFuzzing": false
}

5/1 2026/09/16 00:08 action If
0m Args:
{
  "WorthFuzzing": false
}

Results:
null

LLM Calls Summary:
Total Calls Total Tokens Avg Tokens Total Duration (Seconds) Avg Duration (Seconds)
Tool Calls Summary:
Total Calls Total Duration (Seconds) Avg Duration (Seconds)