mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
synced 2025-01-04 04:02:26 +00:00
Rename kmemleak_initialized to kmemleak_late_initialized
The old name is confusing because it implies the completion of earlier kmemleak_init(), the new name update to kmemleak_late_initial represents the completion of kmemleak_late_init(). No functional changes. Link: https://lkml.kernel.org/r/20230815144128.3623103-3-xiaolei.wang@windriver.com Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com> Acked-by: Catalin Marinas <catalin.marinas@arm.com> Cc: Alexander Potapenko <glider@google.com> Cc: Andrey Konovalov <andreyknvl@gmail.com> Cc: Vlastimil Babka <vbabka@suse.cz> Cc: Zhaoyang Huang <zhaoyang.huang@unisoc.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
This commit is contained in:
parent
835bc157da
commit
d160ef71b4
@ -218,7 +218,7 @@ static int kmemleak_enabled = 1;
|
||||
/* same as above but only for the kmemleak_free() callback */
|
||||
static int kmemleak_free_enabled = 1;
|
||||
/* set in the late_initcall if there were no errors */
|
||||
static int kmemleak_initialized;
|
||||
static int kmemleak_late_initialized;
|
||||
/* set if a kmemleak warning was issued */
|
||||
static int kmemleak_warning;
|
||||
/* set if a fatal kmemleak error has occurred */
|
||||
@ -2057,7 +2057,7 @@ static void kmemleak_disable(void)
|
||||
kmemleak_enabled = 0;
|
||||
|
||||
/* check whether it is too early for a kernel thread */
|
||||
if (kmemleak_initialized)
|
||||
if (kmemleak_late_initialized)
|
||||
schedule_work(&cleanup_work);
|
||||
else
|
||||
kmemleak_free_enabled = 0;
|
||||
@ -2122,7 +2122,7 @@ void __init kmemleak_init(void)
|
||||
*/
|
||||
static int __init kmemleak_late_init(void)
|
||||
{
|
||||
kmemleak_initialized = 1;
|
||||
kmemleak_late_initialized = 1;
|
||||
|
||||
debugfs_create_file("kmemleak", 0644, NULL, NULL, &kmemleak_fops);
|
||||
|
||||
@ -2130,7 +2130,7 @@ static int __init kmemleak_late_init(void)
|
||||
/*
|
||||
* Some error occurred and kmemleak was disabled. There is a
|
||||
* small chance that kmemleak_disable() was called immediately
|
||||
* after setting kmemleak_initialized and we may end up with
|
||||
* after setting kmemleak_late_initialized and we may end up with
|
||||
* two clean-up threads but serialized by scan_mutex.
|
||||
*/
|
||||
schedule_work(&cleanup_work);
|
||||
|
Loading…
Reference in New Issue
Block a user