From: Kalle Valo <kvalo@codeaurora.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<zajec5@gmail.com>, <hauke@hauke-m.de>, <linville@tuxdriver.com>,
<wanghaibin.wang@huawei.com>
Subject: Re: [PATCH 1/2] bcma: Fix memory leak for internally-handled cores
Date: Sat, 21 Aug 2021 13:05:42 +0300 [thread overview]
Message-ID: <877dgfun7t.fsf@codeaurora.org> (raw)
In-Reply-To: <8943a493-aee8-3fe5-e63a-f3b61eaead14@huawei.com> (Zenghui Yu's message of "Sat, 21 Aug 2021 11:28:09 +0800")
Zenghui Yu <yuzenghui@huawei.com> writes:
> On 2021/7/27 10:52, Zenghui Yu wrote:
>> kmemleak reported that dev_name() of internally-handled cores were leaked
>> on driver unbinding. Let's use device_initialize() to take refcounts for
>> them and put_device() to properly free the related stuff.
>
> Could this be picked as a fix for v5.14 (_if_ it does fix something)?
Why should this go to v5.14? Most probably it's too late for v5.14
anyway.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-08-21 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 2:52 two small bcma patches Zenghui Yu
2021-07-27 2:52 ` [PATCH 1/2] bcma: Fix memory leak for internally-handled cores Zenghui Yu
2021-08-21 3:28 ` Zenghui Yu
2021-08-21 10:05 ` Kalle Valo [this message]
2021-08-23 3:56 ` Zenghui Yu
2021-08-29 11:45 ` Kalle Valo
2021-07-27 2:52 ` [PATCH 2/2] bcma: Drop the unused parameter of bcma_scan_read32() Zenghui Yu
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=877dgfun7t.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.com \
--cc=zajec5@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).