From: Steven Rostedt <rostedt@goodmis.org>
To: Chen Jun <chenjun102@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
<rui.xiang@huawei.com>
Subject: Re: [PATCH] trace: Fix a kmemleak noise
Date: Wed, 24 Nov 2021 10:16:16 -0500 [thread overview]
Message-ID: <20211124101616.618ee8f2@gandalf.local.home> (raw)
In-Reply-To: <20211124140801.87121-1-chenjun102@huawei.com>
On Wed, 24 Nov 2021 14:08:01 +0000
Chen Jun <chenjun102@huawei.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
next prev parent reply other threads:[~2021-11-24 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 14:08 Chen Jun
2021-11-24 15:16 ` Steven Rostedt [this message]
2021-11-25 1:48 ` chenjun (AM)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211124101616.618ee8f2@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chenjun102@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rui.xiang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®