From: Vlastimil Babka <vbabka@suse.cz>
To: "zhaoyang.huang" <zhaoyang.huang@unisoc.com>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Matthew Wilcox <willy@infradead.org>,
Marco Elver <elver@google.com>,
Imran Khan <imran.f.khan@oracle.com>,
Dmitry Vyukov <dvyukov@google.com>,
Zhaoyang Huang <huangzhaoyang@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
ke.wang@unisoc.com, steve.kang@unisoc.com
Subject: Re: [PATCH] mm: add stackdepot information on page->private for tracking
Date: Fri, 7 Oct 2022 12:08:53 +0200 [thread overview]
Message-ID: <cd103df8-d0da-ab15-5755-c20631055986@suse.cz> (raw)
In-Reply-To: <1665026390-16096-1-git-send-email-zhaoyang.huang@unisoc.com>
On 10/6/22 05:19, zhaoyang.huang wrote:
> From: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
>
> Private is vacant for most of Non-LRU pages while the user has explicitly
> operation on page->private via set_page_private, I would like introduce
> stackdepot information on page->private for a simplified tracking mechanism
> which could be help for kernel driver's memory leak.
>
> Signed-off-by: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
This duplicates the existing page_owner functionality in a way that
unconditionally adds overhead to all kernels that have CONFIG_STACKDEPOT
enabled build-time (and also misses the need to initialize stackdepot properly).
Also wouldn't be suprised if some existing page->private users were actually
confused by the field suddenly being non-zero without their own action.
> ---
> mm/page_alloc.c | 28 +++++++++++++++++++++++++++-
> 1 file changed, 27 insertions(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index e5486d4..b79a503 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -75,6 +75,7 @@
> #include <linux/khugepaged.h>
> #include <linux/buffer_head.h>
> #include <linux/delayacct.h>
> +#include <linux/stackdepot.h>
> #include <asm/sections.h>
> #include <asm/tlbflush.h>
> #include <asm/div64.h>
> @@ -2464,6 +2465,25 @@ static inline bool should_skip_init(gfp_t flags)
> return (flags & __GFP_SKIP_ZERO);
> }
>
> +#ifdef CONFIG_STACKDEPOT
> +static noinline depot_stack_handle_t set_track_prepare(void)
> +{
> + depot_stack_handle_t trace_handle;
> + unsigned long entries[16];
> + unsigned int nr_entries;
> +
> + nr_entries = stack_trace_save(entries, ARRAY_SIZE(entries), 3);
> + trace_handle = stack_depot_save(entries, nr_entries, GFP_NOWAIT);
> +
> + return trace_handle;
> +}
> +#else
> +static inline depot_stack_handle_t set_track_prepare(void)
> +{
> + return 0;
> +}
> +#endif
> +
> inline void post_alloc_hook(struct page *page, unsigned int order,
> gfp_t gfp_flags)
> {
> @@ -2471,8 +2491,14 @@ inline void post_alloc_hook(struct page *page, unsigned int order,
> !should_skip_init(gfp_flags);
> bool init_tags = init && (gfp_flags & __GFP_ZEROTAGS);
> int i;
> + depot_stack_handle_t stack_handle = set_track_prepare();
>
> - set_page_private(page, 0);
> + /*
> + * Don't worry, user will cover private directly without checking
> + * this field and has ability to trace the page. This also will not
> + * affect expected state when freeing
> + */
> + set_page_private(page, stack_handle);
> set_page_refcounted(page);
>
> arch_alloc_page(page, order);
next prev parent reply other threads:[~2022-10-07 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 3:19 zhaoyang.huang
2022-10-07 10:08 ` Vlastimil Babka [this message]
2022-10-09 2:25 ` Zhaoyang Huang
2022-10-10 8:57 ` Vlastimil Babka
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=cd103df8-d0da-ab15-5755-c20631055986@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=huangzhaoyang@gmail.com \
--cc=imran.f.khan@oracle.com \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=steve.kang@unisoc.com \
--cc=willy@infradead.org \
--cc=zhaoyang.huang@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