From: Kalle Valo <kvalo@codeaurora.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
b43-dev@lists.infradead.org, netdev@vger.kernel.org,
"Jia-Ju Bai" <baijiaju1990@163.com>, "Michael Büsch" <m@bues.ch>
Subject: Re: [PATCH] b43: Fix memory leaks in b43_bus_dev_ssb_init and b43_bus_dev_bcma_init
Date: Mon, 14 Mar 2016 08:18:58 +0200 [thread overview]
Message-ID: <87a8m1mvjh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1457716477-6287-1-git-send-email-sudipm.mukherjee@gmail.com> (Sudip Mukherjee's message of "Fri, 11 Mar 2016 22:44:37 +0530")
Sudip Mukherjee <sudipm.mukherjee@gmail.com> writes:
> From: Jia-Ju Bai <baijiaju1990@163.com>
>
> The memory allocated by kzalloc in b43_bus_dev_ssb_init and
> b43_bus_dev_bcma_init is not freed.
> This patch fixes the bug by adding kfree in b43_ssb_remove,
> b43_bcma_remove and error handling code of b43_bcma_probe.
>
> Thanks Michael for his suggestion.
>
> Signed-off-by: Jia-Ju Bai <baijiaju1990@163.com>
> Acked-by: Michael Büsch <m@bues.ch>
> Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
If no objections I'm planning to queue this to 4.6-rc2.
--
Kalle Valo
next prev parent reply other threads:[~2016-03-14 6:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 17:14 [PATCH] b43: Fix memory leaks in b43_bus_dev_ssb_init and b43_bus_dev_bcma_init Sudip Mukherjee
2016-03-14 6:18 ` Kalle Valo [this message]
2016-03-23 15:51 ` b43: Fix memory leaks in b43_bus_dev_ssb_init andb43_bus_dev_bcma_init Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2016-01-12 1:01 [PATCH] b43: Fix memory leaks in b43_bus_dev_ssb_init and b43_bus_dev_bcma_init Jia-Ju Bai
2016-01-12 5:44 ` Michael Büsch
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=87a8m1mvjh.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=b43-dev@lists.infradead.org \
--cc=baijiaju1990@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--cc=netdev@vger.kernel.org \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).