[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49f77efc-8375-8fc8-aa89-9814bfbfe5bc@lca.pw>
Date: Wed, 27 Mar 2019 14:02:27 -0400
From: Qian Cai <cai@....pw>
To: Catalin Marinas <catalin.marinas@....com>,
Michal Hocko <mhocko@...nel.org>
Cc: akpm@...ux-foundation.org, cl@...ux.com, willy@...radead.org,
penberg@...nel.org, rientjes@...gle.com, iamjoonsoo.kim@....com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] kmemleak: survive in a low-memory situation
On 3/27/19 1:29 PM, Catalin Marinas wrote:
> From dc4194539f8191bb754901cea74c86e7960886f8 Mon Sep 17 00:00:00 2001
> From: Catalin Marinas <catalin.marinas@....com>
> Date: Wed, 27 Mar 2019 17:20:57 +0000
> Subject: [PATCH] mm: kmemleak: Add an emergency allocation pool for kmemleak
> objects
>
> This patch adds an emergency pool for struct kmemleak_object in case the
> normal kmem_cache_alloc() fails under the gfp constraints passed by the
> slab allocation caller. The patch also removes __GFP_NOFAIL which does
> not play well with other gfp flags (introduced by commit d9570ee3bd1d,
> "kmemleak: allow to coexist with fault injection").
>
> Suggested-by: Michal Hocko <mhocko@...nel.org>
> Signed-off-by: Catalin Marinas <catalin.marinas@....com>
It takes 2 runs of LTP oom01 tests to disable kmemleak.
Powered by blists - more mailing lists