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>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Liu Shixin <liushixin2@huawei.com>
Subject: [PATCH v2 0/4] Some bugfix about kmemleak
Date: Sun, 8 Oct 2023 10:33:13 +0800 [thread overview]
Message-ID: <20231008023317.3015699-1-liushixin2@huawei.com> (raw)
Some bugfix to improve the accuracy of detection and the print info of
debug mode.
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 (4):
bootmem: use kmemleak_free_part_phys in put_page_bootmem
bootmem: use kmemleak_free_part_phys in free_bootmem_page
mm/kmemleak: fix partially freeing unknown object warning
mm/kmemleak: fix print format of pointer in pr_debug()
include/linux/bootmem_info.h | 2 +-
mm/bootmem_info.c | 2 +-
mm/kmemleak.c | 37 +++++++++++++++++++++---------------
3 files changed, 24 insertions(+), 17 deletions(-)
--
2.25.1
next reply other threads:[~2023-10-08 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 2:33 Liu Shixin [this message]
2023-10-08 2:33 ` [PATCH v2 1/4] bootmem: use kmemleak_free_part_phys in put_page_bootmem Liu Shixin
2023-10-08 2:33 ` [PATCH v2 2/4] bootmem: use kmemleak_free_part_phys in free_bootmem_page Liu Shixin
2023-10-08 2:33 ` [PATCH v2 3/4] mm/kmemleak: fix partially freeing unknown object warning Liu Shixin
2023-10-09 14:58 ` Catalin Marinas
2023-10-08 2:33 ` [PATCH v2 4/4] mm/kmemleak: fix print format of pointer in pr_debug() Liu Shixin
2023-10-09 13:25 ` 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=20231008023317.3015699-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 \
/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
all inboxes | Powered by JetHome®