[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c6203b3-5f25-d3d1-aefa-d975201c7637@suse.cz>
Date: Tue, 5 Oct 2021 12:02:52 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Miaohe Lin <linmiaohe@...wei.com>, akpm@...ux-foundation.org,
cl@...ux.com, penberg@...nel.org, rientjes@...gle.com,
iamjoonsoo.kim@....com
Cc: gregkh@...uxfoundation.org, faiyazm@...eaurora.org,
andreyknvl@...il.com, ryabinin.a.a@...il.com, thgarnie@...gle.com,
keescook@...omium.org, bharata@...ux.ibm.com, guro@...com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/5] mm, slub: fix potential memoryleak in
kmem_cache_open()
On 9/16/21 14:39, Miaohe Lin wrote:
> In error path, the random_seq of slub cache might be leaked. Fix this by
> using __kmem_cache_release() to release all the relevant resources.
>
> Fixes: 210e7a43fa90 ("mm: SLUB freelist randomization")
> Signed-off-by: Miaohe Lin <linmiaohe@...wei.com>
Reviewed-by: Vlastimil Babka <vbabka@...e.cz>
> ---
> mm/slub.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index a56a6423d4e8..bf1793fb4ce5 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -4210,8 +4210,8 @@ static int kmem_cache_open(struct kmem_cache *s, slab_flags_t flags)
> if (alloc_kmem_cache_cpus(s))
> return 0;
>
> - free_kmem_cache_nodes(s);
> error:
> + __kmem_cache_release(s);
> return -EINVAL;
> }
>
>
Powered by blists - more mailing lists