linux-kernel - Re: [PATCH] mm: percpu: use kmemleak_ignore_phys() instead of kmemleak

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]

Date:   Tue, 5 Jul 2022 14:20:00 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Patrick Wang <patrick.wang.shcn@...il.com>
Cc:     dennis@...nel.org, tj@...nel.org, cl@...ux.com,
        catalin.marinas@....com, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: percpu: use kmemleak_ignore_phys() instead of
 kmemleak_free()

On Tue,  5 Jul 2022 19:31:58 +0800 Patrick Wang <patrick.wang.shcn@...il.com> wrote:

> Kmemleak recently added a rbtree to store the objects
> allocted with physical address. Those objects can't be
> freed with kmemleak_free(). Use kmemleak_ignore_phys()
> instead of kmemleak_free() for those objects.

Thanks.  What are the user-visible runtime effects of this?

And are we able to identify a commit for the Fixes: line?