From: Liu Shixin <liushixin2@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Patrick Wang <patrick.wang.shcn@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Liu Shixin <liushixin2@huawei.com>
Subject: [PATCH v3 0/7] Some bugfix about kmemleak
Date: Wed, 18 Oct 2023 18:29:45 +0800 [thread overview]
Message-ID: <20231018102952.3339837-1-liushixin2@huawei.com> (raw)
Some bugfix about kmemleak and the print info of debug mode.
v2->v3: Split __create_object into two function[4] and use kmemleak_lock to
fix partially freeing unknown object warning[7]. And add a new patch
to fix an inccorrect use of kmem_cache_free[5].
v1->v2: Split the first patch suggested by Andrew. And fix the format of
the last two patches suggested by Catalin. Use mutex in patch[3]
because there are memory allocation with flag GFP_KERNEL.
Liu Shixin (7):
bootmem: use kmemleak_free_part_phys in put_page_bootmem
bootmem: use kmemleak_free_part_phys in free_bootmem_page
mm/kmemleak: fix print format of pointer in pr_debug()
mm: kmemleak: split __create_object into two functions
mm: kmemleak: use mem_pool_free() to free object
mm: kmemleak: add __find_and_remove_object()
mm/kmemleak: fix partially freeing unknown object warning
include/linux/bootmem_info.h | 2 +-
mm/bootmem_info.c | 2 +-
mm/kmemleak.c | 154 +++++++++++++++++++++++------------
3 files changed, 106 insertions(+), 52 deletions(-)
--
2.25.1
next reply other threads:[~2023-10-18 9:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 10:29 Liu Shixin [this message]
2023-10-18 10:29 ` [PATCH v3 1/7] bootmem: use kmemleak_free_part_phys in put_page_bootmem Liu Shixin
2023-10-18 10:29 ` [PATCH v3 2/7] bootmem: use kmemleak_free_part_phys in free_bootmem_page Liu Shixin
2023-10-18 10:29 ` [PATCH v3 3/7] mm/kmemleak: fix print format of pointer in pr_debug() Liu Shixin
2023-10-18 10:29 ` [PATCH v3 4/7] mm: kmemleak: split __create_object into two functions Liu Shixin
2023-10-18 15:42 ` Catalin Marinas
2023-10-18 10:29 ` [PATCH v3 5/7] mm: kmemleak: use mem_pool_free() to free object Liu Shixin
2023-10-18 15:48 ` Catalin Marinas
2023-10-18 15:57 ` Catalin Marinas
2023-10-18 16:22 ` Andrew Morton
2023-10-18 16:34 ` Catalin Marinas
2023-10-18 10:29 ` [PATCH v3 6/7] mm: kmemleak: add __find_and_remove_object() Liu Shixin
2023-10-18 15:51 ` Catalin Marinas
2023-10-18 10:29 ` [PATCH v3 7/7] mm/kmemleak: fix partially freeing unknown object warning Liu Shixin
2023-10-18 16:39 ` 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=20231018102952.3339837-1-liushixin2@huawei.com \
--to=liushixin2@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patrick.wang.shcn@gmail.com \
--cc=wangkefeng.wang@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