[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230815144128.3623103-1-xiaolei.wang@windriver.com>
Date: Tue, 15 Aug 2023 22:41:26 +0800
From: Xiaolei Wang <xiaolei.wang@...driver.com>
To: catalin.marinas@....com, akpm@...ux-foundation.org, vbabka@...e.cz,
glider@...gle.com, andreyknvl@...il.com, zhaoyang.huang@...soc.com
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/2] mm/kmemleak: use object_cache instead of kmemleak_initialized
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 V3:
The comment in set_track_prepare() in patch1 is updated to
/*
* Use object_cache to determine whether kmemleak_init() has
* been invoked.stack_depot_early_init() is called before
* kmemleak_init() in mm_core_init().
*/
Updated the commit log in patch2, Rename kmemleak_initialized to
kmemleak_late_initialized indicates that kmemleak_late_init() is complete
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 | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
--
2.25.1
Powered by blists - more mailing lists