From: Kalle Valo <kvalo@codeaurora.org>
To: Colin King <colin.king@canonical.com>
Cc: kernel-janitors@vger.kernel.org,
Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Ganesh Sesetti <gseset@codeaurora.org>,
John Crispin <john@phrozen.org>,
Karthikeyan Periyasamy <periyasa@codeaurora.org>,
ath11k@lists.infradead.org
Subject: Re: [PATCH][next] ath11k: fix memory leak on reg_info
Date: Wed, 18 Dec 2019 17:52:26 +0000 (UTC) [thread overview]
Message-ID: <20191218175226.B5379C4479D@smtp.codeaurora.org> (raw)
In-Reply-To: <20191212183228.105993-1-colin.king@canonical.com>
Colin King <colin.king@canonical.com> wrote:
> Currently a return path is leaking the previously allocate reg_info. Fix
> this by exiting via the return path mem_free. Since the return value ret
> is defaulted to 0, there is no need to re-assign ret to the 0 before
> the goto.
>
> Addresses-Coverity: ("Resource leak")
> Fixes: d5c65159f289 ("ath11k: driver for Qualcomm IEEE 802.11ax devices")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
b5316db229d5 ath11k: fix memory leak on reg_info
--
https://patchwork.kernel.org/patch/11289073/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-12-18 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 18:32 [PATCH][next] ath11k: fix memory leak on reg_info Colin King
2019-12-12 18:32 ` Colin King
2019-12-18 17:52 ` Kalle Valo
2019-12-18 17:52 ` Kalle Valo
2019-12-18 17:52 ` Kalle Valo [this message]
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=20191218175226.B5379C4479D@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=gseset@codeaurora.org \
--cc=john@phrozen.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=periyasa@codeaurora.org \
--cc=pradeepc@codeaurora.org \
/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.