From: Catalin Marinas <catalin.marinas@arm.com>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, vbabka@suse.cz, peterz@infradead.org,
nathan@kernel.org, ke.wang@unisoc.com, huangzhaoyang@gmail.com,
zhaoyang.huang@unisoc.com
Subject: Re: + mm-use-stack_depot_early_init-for-kmemleak.patch added to mm-hotfixes-unstable branch
Date: Thu, 19 Jan 2023 14:40:17 +0000 [thread overview]
Message-ID: <Y8lWUVIcOasoLYEZ@arm.com> (raw)
In-Reply-To: <a6ff1869-d90e-3d3c-b023-3a95b4bc7eaf@alu.unizg.hr>
On Thu, Jan 19, 2023 at 02:02:29PM +0100, Mirsad Goran Todorovac wrote:
> On 18.1.2023. 1:19, Andrew Morton wrote:
> > --- a/mm/kmemleak.c~mm-use-stack_depot_early_init-for-kmemleak
> > +++ a/mm/kmemleak.c
> > @@ -2070,8 +2070,10 @@ static int __init kmemleak_boot_config(c
> > return -EINVAL;
> > if (strcmp(str, "off") == 0)
> > kmemleak_disable();
> > - else if (strcmp(str, "on") == 0)
> > + else if (strcmp(str, "on") == 0) {
> > kmemleak_skip_disable = 1;
> > + stack_depot_want_early_init();
> > + }
> > else
> > return -EINVAL;
> > return 0;
> > _
> >
> > Patches currently in -mm which might be from zhaoyang.huang@unisoc.com are
> >
> > mm-use-stack_depot_early_init-for-kmemleak.patch
>
> Please note that this patch activates stack_depot_want_early_init() only when
> kernel boot param "kmemleak=on" is used.
>
> When the following configuration is used:
>
> CONFIG_HAVE_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=16000
> # CONFIG_DEBUG_KMEMLEAK_TEST is not set
> # CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF is not set
> CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN=y
Indeed, I commented here already:
https://lore.kernel.org/all/Y8gDdnpvkCKvVV1t@arm.com/
--
Catalin
next prev parent reply other threads:[~2023-01-19 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 0:19 + mm-use-stack_depot_early_init-for-kmemleak.patch added to mm-hotfixes-unstable branch Andrew Morton
2023-01-19 13:02 ` Mirsad Goran Todorovac
2023-01-19 14:40 ` Catalin Marinas [this message]
2023-01-19 14:51 ` Vlastimil Babka
2023-01-19 15:03 ` Mirsad Goran Todorovac
2023-01-19 17:01 ` Mirsad Goran Todorovac
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=Y8lWUVIcOasoLYEZ@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=huangzhaoyang@gmail.com \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=mm-commits@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=vbabka@suse.cz \
--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 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.