From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Wei Yongjun <weiyongjun1@huawei.com>,
Chen Jun <chenjun102@huawei.com>,
Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
kernel@openvz.org
Subject: [PATCH 0/2] kmemleak: support for percpu memory leak detect
Date: Thu, 25 Jul 2024 12:12:14 +0800 [thread overview]
Message-ID: <20240725041223.872472-1-ptikhomirov@virtuozzo.com> (raw)
This is a rework of this series:
https://lore.kernel.org/lkml/20200921020007.35803-1-chenjun102@huawei.com/
Originally I was investigating a percpu leak on our customer nodes and
having this functionality was a huge help, which lead to this fix [1].
So probably it's a good idea to have it in mainstream too, especially as
after [2] it became much easier to implement (we already have a separate
tree for percpu pointers).
commit 0af8c09c89681 ("netfilter: x_tables: fix percpu counter block
leak on error path when creating new netns") [1]
commit 39042079a0c24 ("kmemleak: avoid RCU stalls when freeing metadata
for per-CPU pointers") [2]
Pavel Tikhomirov (2):
kmemleak: enable tracking for percpu pointers
kmemleak-test: add percpu leak
mm/kmemleak.c | 153 +++++++++++++++++++------------
samples/kmemleak/kmemleak-test.c | 2 +
2 files changed, 96 insertions(+), 59 deletions(-)
--
2.45.2
next reply other threads:[~2024-07-25 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 4:12 Pavel Tikhomirov [this message]
2024-07-25 4:12 ` [PATCH 1/2] kmemleak: enable tracking for percpu pointers Pavel Tikhomirov
2024-07-30 14:15 ` Catalin Marinas
2024-07-31 2:30 ` Pavel Tikhomirov
2024-07-25 4:12 ` [PATCH 2/2] kmemleak-test: add percpu leak Pavel Tikhomirov
2024-07-30 14:17 ` 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=20240725041223.872472-1-ptikhomirov@virtuozzo.com \
--to=ptikhomirov@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=catalin.marinas@arm.com \
--cc=chenjun102@huawei.com \
--cc=kernel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox