From: Sudip Mukherjee <redacted>
On error we jumped to the label bcma_out and returned the error code but
we missed freeing dev.
Signed-off-by: Sudip Mukherjee <redacted>
---
drivers/net/wireless/broadcom/b43/main.c | 1 +
1 file changed, 1 insertion(+)
On 18 February 2016 at 13:34, Sudip Mukherjee
[off-list ref] wrote:
From: Sudip Mukherjee <redacted>
On error we jumped to the label bcma_out and returned the error code but
we missed freeing dev.
What if b43_one_core_attach fails? Won't we miss kfree then as well?
Shouldn't you simply improve error path and maybe use an additional
label? Also may we be missing a proper free in b43_bcma_remove as
well?
Your patch subject could also be a bit more descriptive (e.g. what
memory leak exactly is it).
From: Michael Büsch <m@bues.ch> Date: 2016-02-18 16:32:45
On Thu, 18 Feb 2016 18:04:36 +0530
Sudip Mukherjee [off-list ref] wrote:
quoted hunk
From: Sudip Mukherjee <redacted>
On error we jumped to the label bcma_out and returned the error code but
we missed freeing dev.
Signed-off-by: Sudip Mukherjee <redacted>
---
drivers/net/wireless/broadcom/b43/main.c | 1 +
1 file changed, 1 insertion(+)
@@ -5671,6 +5671,7 @@ static int b43_bcma_probe(struct bcma_device *core)wl=b43_wireless_init(dev);if(IS_ERR(wl)){err=PTR_ERR(wl);+kfree(dev);gotobcma_out;}
We recently had a patch that fixes this, among more leaks. Subject:
[PATCH v2 resend] b43: Fix memory leaks in b43_bus_dev_ssb_init and
b43_bus_dev_bcma_init
Please test that patch instead, so we can finally apply it.
It needs to be tested on both ssb and bcma. Come on. This isn't too
hard. :) Please somebody with any hardware test it. (I currently don't
have any b43 hardware)
--
Michael