From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Aaradhana Sahu <aaradhana.sahu@oss.qualcomm.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, jjohnson@kernel.org,
baochen.qiang@oss.qualcomm.com,
vasanthakumar.thiagarajan@oss.qualcomm.com
Subject: Re: [PATCH ath-next v2] wifi: ath12k: Fix NAPI resource leaks in AHB external IRQ paths
Date: Fri, 9 Oct 2026 13:17:14 -0700 [thread overview]
Message-ID: <40903cb4-e39e-43de-be81-27a5f29aeeac@oss.qualcomm.com> (raw)
In-Reply-To: <20261001045423.493121-1-aaradhana.sahu@oss.qualcomm.com>
On 9/30/2026 9:54 PM, Aaradhana Sahu wrote:
> static int ath12k_ahb_config_irq(struct ath12k_base *ab)
> @@ -1353,7 +1382,7 @@ static int ath12k_ahb_probe(struct platform_device *pdev)
> ret = ab_ahb->device_family_ops->arch_init(ab);
> if (ret) {
> ath12k_err(ab, "AHB arch_init failed %d\n", ret);
> - goto err_rproc_deconfigure;
> + goto err_free_irq;
> }
>
> ret = ath12k_core_init(ab);
> @@ -1367,6 +1396,9 @@ static int ath12k_ahb_probe(struct platform_device *pdev)
> err_deinit_arch:
> ab_ahb->device_family_ops->arch_deinit(ab);
>
> +err_free_irq:
my review agent notes:
**Misleading label name `err_free_irq`**
The label name implies IRQ teardown, but the IRQs registered via
`devm_request_irq()` are automatically freed on device detach — no explicit
free is needed here. This label only frees NAPI/netdev resources. Suggest
renaming to `err_free_ext_napi` or `err_free_napi` to match the actual
operation and avoid confusing future readers.
No need to post a new version just for this -- I'll make this change in my
'pending' branch if the reviewers are otherwise ok with your patch
> + ath12k_ahb_free_ext_napi(ab);
> +
> err_rproc_deconfigure:
> mutex_lock(&ath12k_rproc_info_lock);
> ath12k_ahb_deconfigure_rproc(ab);
next prev parent reply other threads:[~2026-10-09 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 4:54 [PATCH ath-next v2] wifi: ath12k: Fix NAPI resource leaks in AHB external IRQ paths Aaradhana Sahu
2026-10-08 17:16 ` Rameshkumar Sundaram
2026-10-09 3:38 ` Aaradhana Sahu
2026-10-09 20:41 ` Jeff Johnson
2026-10-12 9:19 ` Aaradhana Sahu
2026-10-09 20:17 ` Jeff Johnson [this message]
2026-10-12 15:00 ` Jeff Johnson
2026-10-12 6:35 ` Baochen Qiang
2026-10-12 8:59 ` Rameshkumar Sundaram
2026-10-13 1:05 ` Jeff Johnson
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=40903cb4-e39e-43de-be81-27a5f29aeeac@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=aaradhana.sahu@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vasanthakumar.thiagarajan@oss.qualcomm.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