From: Chen Jun <chenjun102@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Cc: <catalin.marinas@arm.com>, <akpm@linux-foundation.org>,
<rui.xiang@huawei.com>, <weiyongjun1@huawei.com>
Subject: [PATCH -next 0/5] mm/kmemleak：support for percpu memory leak detect
Date: Mon, 21 Sep 2020 02:00:02 +0000 [thread overview]
Message-ID: <20200921020007.35803-1-chenjun102@huawei.com> (raw)
Currently the reporting of the percpu chunks leaking problem are not supported.
This patch set introduce this feature.
PATCH 1-2 do some cleanup to current kmemleak.
PATCH 3 make percpu memleak works.
PATCH 4-5 add test case for percpu memleak detector.
Following links are some real cases detected by it:
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71e843295c680898959b22dc877ae3839cc22470
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=667e57da358f61b6966e12e925a69e42d912e8bb
*** BLURB HERE ***
Chen Jun (1):
mm/kmemleak-test: Add a test case for alloc_percpu
Wei Yongjun (4):
mm/kmemleak: make create_object return void
mm/kmemleak: skip update_checksum for OBJECT_NO_SCAN objects
mm/kmemleak: Add support for percpu memory leak detect
mm/kmemleak-test: use %px instead of %p in print
mm/kmemleak-test.c | 37 ++++++++++++----------
mm/kmemleak.c | 79 +++++++++++++++++++++++++++++++++++++---------
2 files changed, 84 insertions(+), 32 deletions(-)
--
2.25.0
next reply other threads:[~2020-09-21 2:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 2:00 Chen Jun [this message]
2020-09-21 2:00 ` [PATCH -next 1/5] mm/kmemleak: make create_object return void Chen Jun
2020-09-22 9:57 ` Catalin Marinas
2020-09-21 2:00 ` [PATCH -next 2/5] mm/kmemleak: skip update_checksum for OBJECT_NO_SCAN objects Chen Jun
2020-09-22 9:03 ` Catalin Marinas
2020-09-21 2:00 ` [PATCH -next 3/5] mm/kmemleak: Add support for percpu memory leak detect Chen Jun
2020-09-22 9:57 ` Catalin Marinas
2020-09-28 14:08 ` chenjun (AM)
2020-09-28 14:16 ` Catalin Marinas
2020-09-21 2:00 ` [PATCH -next 4/5] mm/kmemleak-test: use %px instead of %p in print Chen Jun
2020-09-22 9:58 ` Catalin Marinas
2020-09-21 2:00 ` [PATCH -next 5/5] mm/kmemleak-test: Add a test case for alloc_percpu Chen Jun
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=20200921020007.35803-1-chenjun102@huawei.com \
--to=chenjun102@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rui.xiang@huawei.com \
--cc=weiyongjun1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.