linux-kernel - Re: [PATCH 1/2] bcma: Fix memory leak for internally-handled cores

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2b218922-45b2-38cc-2a80-4d339949deed@huawei.com>
Date:   Mon, 23 Aug 2021 11:56:34 +0800
From:   Zenghui Yu <yuzenghui@...wei.com>
To:     Kalle Valo <kvalo@...eaurora.org>
CC:     <linux-wireless@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <zajec5@...il.com>, <hauke@...ke-m.de>, <linville@...driver.com>,
        <wanghaibin.wang@...wei.com>
Subject: Re: [PATCH 1/2] bcma: Fix memory leak for internally-handled cores

On 2021/8/21 18:05, Kalle Valo wrote:
> Zenghui Yu <yuzenghui@...wei.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.

No worries. It's not urgent and just that I didn't realize we're
already at rc7 now.

The patch has been on the list for about 4 weeks and I'd appreciate
any review comments from maintainers.

Zenghui