From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Kamil Bienkiewicz <perceivalpercy@gmail.com>,
linux-wireless@vger.kernel.org,
Jeff Johnson <jjohnson@kernel.org>
Cc: ath12k@lists.infradead.org
Subject: Re: [BUG] ath12k: NULL deref in ath12k_mac_op_hw_scan() when a scan is requested during firmware recovery (IPQ5332 + QCN9274)
Date: Fri, 31 Jul 2026 10:27:36 -0700 [thread overview]
Message-ID: <440d1bf6-4b6e-4c87-b80d-4e6dc1a65639@oss.qualcomm.com> (raw)
In-Reply-To: <20260731094141.2410630-1-perceivalpercy@gmail.com>
On 7/31/2026 2:41 AM, Kamil Bienkiewicz wrote:
> Hi,
>
> A scan request that arrives while the device is recovering from a firmware
> crash oopses the kernel in ath12k_mac_op_hw_scan(). Because the oops reboots
> the AP and the same firmware crash tends to recur on the next boot, this
> presents as a boot loop rather than a one-off crash.
>
> Hardware: GL.iNet GL-BE9300 (Flint 3) - IPQ5332 (ath12k_wifi7 AHB, 2.4 GHz)
> + QCN9274 (ath12k_wifi7_pci, 5/6 GHz)
> Kernel: 6.18.39, OpenWrt build, ath12k as out-of-tree module (Tainted: O)
Unless you reproduce this with the upstream kernel you should be reporting
this to the OpenWrt team, not here.
If you reproduce with the upstream kernel, see:
https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath12k/bugreport.html
/jeff
next prev parent reply other threads:[~2026-07-31 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 9:41 [BUG] ath12k: NULL deref in ath12k_mac_op_hw_scan() when a scan is requested during firmware recovery (IPQ5332 + QCN9274) Kamil Bienkiewicz
2026-07-31 17:27 ` Jeff Johnson [this message]
2026-07-31 17:51 ` Kamil Bienkiewicz
2026-07-31 18:18 ` Jeff Johnson
2026-07-31 18:55 ` Kamil Bienkiewicz
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=440d1bf6-4b6e-4c87-b80d-4e6dc1a65639@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=perceivalpercy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox