From: Xiaolei Wang <xiaolei.wang@windriver.com>
To: catalin.marinas@arm.com, akpm@linux-foundation.org,
vbabka@suse.cz, glider@google.com, andreyknvl@gmail.com,
zhaoyang.huang@unisoc.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] mm/kmemleak: use object_cache instead of kmemleak_initialized
Date: Tue, 15 Aug 2023 13:13:56 +0800 [thread overview]
Message-ID: <20230815051358.802035-1-xiaolei.wang@windriver.com> (raw)
use object_cache instead of kmemleak_initialized to check in
set_track_prepare(), so that memory leaks after kmemleak_init()
can be recorded and Rename kmemleak_initialized to
kmemleak_late_initialized
unreferenced object 0xc674ca80 (size 64):
comm "swapper/0", pid 1, jiffies 4294938337 (age 204.880s)
hex dump (first 32 bytes):
80 55 75 c6 80 54 75 c6 00 55 75 c6 80 52 75 c6 .Uu..Tu..Uu..Ru.
00 53 75 c6 00 00 00 00 00 00 00 00 00 00 00 00 .Su..........
Change in V2:
Delete patch1 in v1 version, change patch2, use object_cache instead of
kmemleak_initialized to check in set_track_prepare(), so that memory leak
after kmemleak_init() can be recorded, and rename kmemleak_initialized to
kmemleak_late_initialized
Xiaolei Wang (2):
mm/kmemleak: use object_cache instead of kmemleak_initialized to check
in set_track_prepare()
Rename kmemleak_initialized to kmemleak_late_initialized
mm/kmemleak.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2023-08-15 5:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 5:13 Xiaolei Wang [this message]
2023-08-15 5:13 ` [PATCH v2 1/2] mm/kmemleak: use object_cache instead of kmemleak_initialized to check in set_track_prepare() Xiaolei Wang
2023-08-15 10:39 ` Catalin Marinas
2023-08-15 5:13 ` [PATCH v2 2/2] Rename kmemleak_initialized to kmemleak_late_initialized Xiaolei Wang
2023-08-15 10:40 ` Catalin Marinas
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=20230815051358.802035-1-xiaolei.wang@windriver.com \
--to=xiaolei.wang@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=zhaoyang.huang@unisoc.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