From: Greg KH <gregkh@linuxfoundation.org>
To: Fangzheng Zhang <fangzheng.zhang@unisoc.com>
Cc: 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>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
tkjos@google.com, Fangzheng Zhang <fangzheng.zhang1003@gmail.com>,
Yuming Han <yuming.han@unisoc.com>
Subject: Re: [PATCH 1/2] mm/slub: Add panic function when slub leaks
Date: Wed, 25 Sep 2024 10:10:51 +0200 [thread overview]
Message-ID: <2024092528-primp-ogle-23c4@gregkh> (raw)
In-Reply-To: <20240925032256.1782-2-fangzheng.zhang@unisoc.com>
On Wed, Sep 25, 2024 at 11:22:55AM +0800, Fangzheng Zhang wrote:
> Perform real-time memory usage monitoring on the slub page
> allocation paths, ie, kmalloc_large_alloced and alloc_slab_page.
> When the usage exceeds the set threshole value, the panic function
> will be triggered.
>
> Signed-off-by: Fangzheng Zhang <fangzheng.zhang@unisoc.com>
> ---
> mm/Kconfig | 11 ++++++++
> mm/slub.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 87 insertions(+)
>
> diff --git a/mm/Kconfig b/mm/Kconfig
> index 09aebca1cae3..60cf72d4f0da 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -255,6 +255,17 @@ config SLUB_TINY
>
> If unsure, say N.
>
> +config SLUB_LEAK_PANIC
> + bool "Trigger panic when slub leaks"
> + default y
> + help
> + 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. Uers
> + can enable and set leak threshold by using the kernel command line
> + parameters "slub.leak_panic" and "slub.leak_panic_threshold".
> +
> config SLAB_MERGE_DEFAULT
> bool "Allow slab caches to be merged"
> default y
> diff --git a/mm/slub.c b/mm/slub.c
> index 21f71cb6cc06..91049f87ab98 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -42,6 +42,9 @@
> #include <kunit/test.h>
> #include <kunit/test-bug.h>
> #include <linux/sort.h>
> +#ifdef CONFIG_SLUB_LEAK_PANIC
> +#include <linux/vmstat.h>
> +#endif
Please redo this to not require #ifdef in .c files, otherwise it gets
very unmaintainable over time.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-25 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 3:22 [PATCH 0/2] Introduce panic function when slub leaks Fangzheng Zhang
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 [this message]
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=2024092528-primp-ogle-23c4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=fangzheng.zhang1003@gmail.com \
--cc=fangzheng.zhang@unisoc.com \
--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 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.