Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 20 May 2019 10:18:05 -0700 (PDT)
From:   David Rientjes <rientjes@google.com>
To:     Qian Cai <cai@lca.pw>
cc:     akpm@linux-foundation.org, cl@linux.com, penberg@kernel.org,
        iamjoonsoo.kim@lge.com, catalin.marinas@arm.com,
        linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] slab: skip kmemleak_object in leaks_show()
In-Reply-To: <20190514144741.39460-1-cai@lca.pw>
Message-ID: <alpine.DEB.2.21.1905201017420.96074@chino.kir.corp.google.com>
References: <20190514144741.39460-1-cai@lca.pw>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, 14 May 2019, Qian Cai wrote:

> Running tests on a debug kernel will usually generate a large number of
> kmemleak objects.
> 
>   # grep kmemleak /proc/slabinfo
>   kmemleak_object   2243606 3436210 ...
> 
> As the result, reading /proc/slab_allocators could easily loop forever
> while processing the kmemleak_object cache and any additional freeing or
> allocating objects will trigger a reprocessing. To make a situation
> worse, soft-lockups could easily happen in this sitatuion which will
> call printk() to allocate more kmemleak objects to guarantee a livelock.
> 
> Since kmemleak_object has a single call site (create_object()), there
> isn't much new information compared with slabinfo. Just skip it.
> 
> Signed-off-by: Qian Cai <cai@lca.pw>

I assume this is now obsolete since commit 7878c231dae0 ("slab: remove 
/proc/slab_allocators").