From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Nicolas Escande <nico.escande@gmail.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath 0/2] fix leaks in some WMI error path
Date: Thu, 30 Apr 2026 14:54:08 -0700 [thread overview]
Message-ID: <67aba8de-9a4e-46bd-936a-688abdb5d01e@oss.qualcomm.com> (raw)
In-Reply-To: <20260424144813.1708214-1-nico.escande@gmail.com>
On 4/24/2026 7:48 AM, Nicolas Escande wrote:
> So this is similar work to what has been posted here [0] for ath12k.
>
> When we use the pattern 'return ath11k_wmi_cmd_send(...)' without
> explicitly checking the return value we fail to free the allocated skb.
>
> This has been split into 2 patches per Jeff's guidance to hopefully
> ease the backporting process.
>
> [0] https://lore.kernel.org/linux-wireless/20260422163258.3013872-1-nico.escande@gmail.com/
>
> Nicolas Escande (2):
> wifi: ath11k: fix leak in error path of some WOW related WMI commands
> wifi: ath11k: fix error path leaks in some WMI calls
>
> drivers/net/wireless/ath/ath11k/wmi.c | 131 ++++++++++++++++++++++----
> 1 file changed, 112 insertions(+), 19 deletions(-)
>
Please repost and include the ath11k list
next prev parent reply other threads:[~2026-04-30 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 14:48 [PATCH ath 0/2] fix leaks in some WMI error path Nicolas Escande
2026-04-24 14:48 ` [PATCH 1/2] wifi: ath11k: fix error path leaks in some WMI WOW calls Nicolas Escande
2026-04-24 14:48 ` [PATCH 2/2] wifi: ath11k: fix error path leaks in some WMI calls Nicolas Escande
2026-04-28 2:53 ` [PATCH ath 0/2] fix leaks in some WMI error path Baochen Qiang
2026-04-28 3:02 ` Baochen Qiang
2026-04-30 21:54 ` Jeff Johnson [this message]
2026-05-02 7:16 ` Nicolas Escande
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=67aba8de-9a4e-46bd-936a-688abdb5d01e@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nico.escande@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