The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Qian Cai <cai@gmx.us>, akpm@linux-foundation.org
Cc: tglx@linutronix.de, yang.shi@linux.alibaba.com, arnd@arndb.de,
	catalin.marinas@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugobjects: avoid recursive calls with kmemleak
Date: Mon, 26 Nov 2018 12:10:14 -0500	[thread overview]
Message-ID: <f42cacfd-e97d-7471-f520-619fbbee63ff@redhat.com> (raw)
In-Reply-To: <20181126165343.2339-1-cai@gmx.us>

On 11/26/2018 11:53 AM, Qian Cai wrote:
> CONFIG_DEBUG_OBJECTS_RCU_HEAD does not play well with kmemleak due to
> recursive calls.
>
> fill_pool
>   kmemleak_ignore
>     make_black_object
>       put_object
>         __call_rcu (kernel/rcu/tree.c)
>           debug_rcu_head_queue
>             debug_object_activate
>               debug_object_init
>                 fill_pool
>                   kmemleak_ignore
>                     make_black_object
>                       ...
>
> Hence, adding SLAB_NOLEAKTRACE to kmem_cache_create() to not register a
> newly allocated debug objects at all.
>
> Suggested-by: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Qian Cai <cai@gmx.us>
> ---
>  lib/debugobjects.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/lib/debugobjects.c b/lib/debugobjects.c
> index eab7727b46ed..55437fd5128b 100644
> --- a/lib/debugobjects.c
> +++ b/lib/debugobjects.c
> @@ -135,7 +135,6 @@ static void fill_pool(void)
>  		if (!new)
>  			return;
>  
> -		kmemleak_ignore(new);
>  		raw_spin_lock_irqsave(&pool_lock, flags);
>  		hlist_add_head(&new->node, &obj_pool);
>  		debug_objects_allocated++;
> @@ -1128,7 +1127,6 @@ static int __init debug_objects_replace_static_objects(void)
>  		obj = kmem_cache_zalloc(obj_cache, GFP_KERNEL);
>  		if (!obj)
>  			goto free;
> -		kmemleak_ignore(obj);
>  		hlist_add_head(&obj->node, &objects);
>  	}
>  
> @@ -1182,7 +1180,8 @@ void __init debug_objects_mem_init(void)
>  
>  	obj_cache = kmem_cache_create("debug_objects_cache",
>  				      sizeof (struct debug_obj), 0,
> -				      SLAB_DEBUG_OBJECTS, NULL);
> +				      SLAB_DEBUG_OBJECTS | SLAB_NOLEAKTRACE,
> +				      NULL);
>  
>  	if (!obj_cache || debug_objects_replace_static_objects()) {
>  		debug_objects_enabled = 0;

Acked-by: Waiman Long <longman@redhat.com>


  reply	other threads:[~2018-11-26 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 16:53 [PATCH] debugobjects: avoid recursive calls with kmemleak Qian Cai
2018-11-26 17:10 ` Waiman Long [this message]
2018-11-26 17:21 ` 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=f42cacfd-e97d-7471-f520-619fbbee63ff@redhat.com \
    --to=longman@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=cai@gmx.us \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yang.shi@linux.alibaba.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