linux-kernel - Re: [PATCH] trace: Fix a kmemleak noise

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: <20211124101616.618ee8f2@gandalf.local.home>
Date:   Wed, 24 Nov 2021 10:16:16 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Chen Jun <chenjun102@...wei.com>
Cc:     <linux-kernel@...r.kernel.org>, <mingo@...hat.com>,
        <rui.xiang@...wei.com>
Subject: Re: [PATCH] trace: Fix a kmemleak noise

On Wed, 24 Nov 2021 14:08:01 +0000
Chen Jun <chenjun102@...wei.com> wrote:

> The reason is elts->pages[i] is alloced by get_zeroed_page.
> and kmemleak will not scan the area alloced by get_zeroed_page.
> The address stored in elts->pages will be regarded as leaked.

Why doesn't kmemleak scan get_zeroed_page? And if that's the case, how does
all the other locations in the kernel that call get_zeroed_page handle this?

-- Steve