From: Kalle Valo <kvalo@codeaurora.org>
To: Alex Dewar <alex.dewar90@gmail.com>
Cc: unlisted-recipients:; (no To-header on input) Alex Dewar
<alex.dewar90@gmail.com>, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ath11k: Fix memory leak on error path
Date: Thu, 8 Oct 2020 10:46:14 +0000 (UTC) [thread overview]
Message-ID: <20201008104614.79150C433FF@smtp.codeaurora.org> (raw)
In-Reply-To: <20201004100218.311653-2-alex.dewar90@gmail.com>
Alex Dewar <alex.dewar90@gmail.com> wrote:
> In ath11k_mac_setup_iface_combinations(), if memory cannot be assigned
> for the variable limits, then the memory assigned to combinations will
> be leaked. Fix this.
>
> Addresses-Coverity-ID: 1497534 ("Resource leaks")
> Fixes: 2626c269702e ("ath11k: add interface_modes to hw_params")
> Signed-off-by: Alex Dewar <alex.dewar90@gmail.com>
Patch applied to wireless-drivers-next.git, thanks.
8431350eee2e ath11k: Fix memory leak on error path
--
https://patchwork.kernel.org/patch/11815579/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-10-08 10:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 10:02 [PATCH 2/2] ath11k: Handle errors if peer creation fails Alex Dewar
2020-10-04 10:02 ` Alex Dewar
2020-10-04 10:02 ` [PATCH 1/2] ath11k: Fix memory leak on error path Alex Dewar
2020-10-04 10:02 ` Alex Dewar
2020-10-08 10:46 ` Kalle Valo
2020-10-08 10:46 ` Kalle Valo [this message]
2020-10-06 7:26 ` [PATCH 2/2] ath11k: Handle errors if peer creation fails Kalle Valo
2020-10-06 7:26 ` Kalle Valo
2020-10-06 8:13 ` Alex Dewar
2020-10-06 8:13 ` Alex Dewar
2020-11-07 11:23 ` Kalle Valo
2020-11-07 11:23 ` Kalle Valo
2020-11-07 13:49 ` Alex Dewar
2020-11-07 13:49 ` Alex Dewar
2020-11-10 18:14 ` Kalle Valo
2020-11-10 18:15 ` Kalle Valo
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=20201008104614.79150C433FF@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=alex.dewar90@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.