linux-kernel - [PATCH 0/2] Bail out in __stack_depot_save() if the stack_table is not allocated and delete the kmemleak_initialized judgment in set_track

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-next>] [day] [month] [year] [list]

Message-Id: <20230810074704.2042664-1-xiaolei.wang@windriver.com>
Date:   Thu, 10 Aug 2023 15:47:02 +0800
From:   Xiaolei Wang <xiaolei.wang@...driver.com>
To:     catalin.marinas@....com, akpm@...ux-foundation.org,
        glider@...gle.com, andreyknvl@...il.com, vbabka@...e.cz,
        zhaoyang.huang@...soc.com
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] Bail out in __stack_depot_save() if the stack_table is not allocated and delete the kmemleak_initialized judgment in set_track_prepare()

patch1 solves the null pointer situation when __stack_depot_save()
is called when the stack_table is not initialized.

patch2 solved there is no call trace for the memory leak which object
is created before the kmemleak_late_init()

Xiaolei Wang (2):
  lib/stackdepot: Bail out in __stack_depot_save() if the stack_table is
    not allocated
  mm/kmemleak: No need to check kmemleak_initialized in
    set_track_prepare()

 lib/stackdepot.c | 2 +-
 mm/kmemleak.c    | 2 --
 2 files changed, 1 insertion(+), 3 deletions(-)

-- 
2.25.1