29-Jun-2026 08:59:01: attempting to guess the base commit by blob hashes
29-Jun-2026 08:59:01: unknown object af5d16055396, stopping base commit search
29-Jun-2026 08:59:01: no candidate base commit is found
29-Jun-2026 08:59:01: considering tree "torvalds"
29-Jun-2026 08:59:01: "torvalds"'s last build: &{"amd64" "torvalds" "https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux" "dc59e4fea9d83f03bad6bddf3fa2e52491777482" "2026-06-28 19:01:31 +0000 UTC" "upstream-apparmor-kasan.config" "" "" "" %!q(bool=true)}
29-Jun-2026 08:59:01: current HEAD: "dc59e4fea9d83f03bad6bddf3fa2e52491777482" (commit date: 2026-06-28 12:01:31 -0700 -0700)
29-Jun-2026 08:59:01: considering "dc59e4fea9d83f03bad6bddf3fa2e52491777482"
29-Jun-2026 09:00:05: series can be applied to "dc59e4fea9d83f03bad6bddf3fa2e52491777482"
29-Jun-2026 09:00:05: result: dc59e4fea9d83f03bad6bddf3fa2e52491777482
29-Jun-2026 09:00:05: continuing with dc59e4fea9d83f03bad6bddf3fa2e52491777482 in torvalds
29-Jun-2026 09:00:11: starting AI patch evaluation...
29-Jun-2026 09:08:00: AI verdict: WorthFuzzing=true (Reason: The patch fixes a deadlock in the MT7921 wireless driver. `mt7921_regd_set_6ghz_power_type` is called from `mt7921_mac_sta_add` and `mt7921_mac_sta_remove`, which are invoked by mac80211 with the `dev->mutex` already held. Previously, it called `mt7921_mcu_regd_update`, which attempted to acquire the same mutex, leading to a deadlock. The patch introduces `__mt7921_mcu_regd_update` to be called when the mutex is already held. This is a functional fix for a deadlock in reachable driver code. The driver can be reached in virtualized environments via the USB interface (`CONFIG_MT7921U`).)