From: Fangzheng Zhang <fangzheng.zhang@unisoc.com>
To: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<tkjos@google.com>, Fangzheng Zhang <fangzheng.zhang@unisoc.com>,
Fangzheng Zhang <fangzheng.zhang1003@gmail.com>,
Yuming Han <yuming.han@unisoc.com>
Subject: [PATCH 0/2] Introduce panic function when slub leaks
Date: Wed, 25 Sep 2024 11:22:54 +0800 [thread overview]
Message-ID: <20240925032256.1782-1-fangzheng.zhang@unisoc.com> (raw)
Hi all,
A method to detect slub leaks by monitoring its usage in real time
on the page allocation path of the slub. When the slub occupancy
exceeds the user-set value, it is considered that the slub is leaking
at this time, and a panic operation will be triggered immediately.
Fangzheng Zhang (2):
mm/slub: Add panic function when slub leaks
Documentation: admin-guide: kernel-parameters: Add parameter
description for slub_leak_panic function
.../admin-guide/kernel-parameters.txt | 15 ++++
mm/Kconfig | 11 ++++++++
mm/slub.c | 76 +++++++++++++++++++
3 files changed, 102 insertions(+)
--
2.17.1
next reply other threads:[~2024-09-25 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 3:22 Fangzheng Zhang [this message]
2024-09-25 3:22 ` [PATCH 1/2] mm/slub: Add " Fangzheng Zhang
2024-09-25 8:10 ` Greg KH
2024-09-25 12:45 ` zhang fangzheng
2024-09-25 8:10 ` Greg KH
2024-09-25 11:39 ` kernel test robot
2024-09-25 12:10 ` kernel test robot
2024-09-25 3:22 ` [PATCH 2/2] Documentation: admin-guide: kernel-parameters: Add parameter description for slub_leak_panic function Fangzheng Zhang
2024-09-25 13:18 ` [PATCH 0/2] Introduce panic function when slub leaks Hyeonggon Yoo
2024-09-26 12:30 ` Vlastimil Babka
2024-09-27 7:28 ` zhang fangzheng
2024-09-27 8:01 ` Hyeonggon Yoo
2024-10-09 1:25 ` 答复: " 韩玉明 (Yuming Han)
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=20240925032256.1782-1-fangzheng.zhang@unisoc.com \
--to=fangzheng.zhang@unisoc.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=fangzheng.zhang1003@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=tkjos@google.com \
--cc=vbabka@suse.cz \
--cc=yuming.han@unisoc.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