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: <877dgfun7t.fsf@codeaurora.org>
Date:   Sat, 21 Aug 2021 13:05:42 +0300
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Zenghui Yu <yuzenghui@...wei.com>
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

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.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches