linux-kernel - Re: [PATCH v2] workqueue: Use the kmem_cache_free() instead of kfree() to release pwq

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] [day] [month] [year] [list]

Message-ID: <ZSguI0D8RUgwlpKc@slm.duckdns.org>
Date:   Thu, 12 Oct 2023 07:34:27 -1000
From:   Tejun Heo <tj@...nel.org>
To:     Zqiang <qiang.zhang1211@...il.com>
Cc:     jiangshanlai@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] workqueue: Use the kmem_cache_free() instead of
 kfree() to release pwq

On Wed, Oct 11, 2023 at 04:27:59PM +0800, Zqiang wrote:
> Currently, the kfree() be used for pwq objects allocated with
> kmem_cache_alloc() in alloc_and_link_pwqs(), this isn't wrong.
> but usually, use "trace_kmem_cache_alloc/trace_kmem_cache_free"
> to track memory allocation and free. this commit therefore use
> kmem_cache_free() instead of kfree() in alloc_and_link_pwqs()
> and also consistent with release of the pwq in rcu_free_pwq().
> 
> Signed-off-by: Zqiang <qiang.zhang1211@...il.com>

Applied to wq/for-6.6-fixes.

Thanks.

-- 
tejun