Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Mon, 9 May 2022 20:20:57 +0900
From:   Hyeonggon Yoo <42.hyeyoo@gmail.com>
To:     Paran Lee <p4ranlee@gmail.com>
Cc:     Christoph Lameter <cl@linux.com>,
        Pekka Enberg <penberg@kernel.org>,
        David Rientjes <rientjes@google.com>,
        Joonsoo Kim <iamjoonsoo.kim@lge.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Vlastimil Babka <vbabka@suse.cz>,
        Roman Gushchin <roman.gushchin@linux.dev>,
        linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org,
        Oliver Glitta <glittao@gmail.com>,
        Austin Kim <austindh.kim@gmail.com>
Subject: Re: [PATCH] slub: kunit catch kmem_cache_alloc failed
Message-ID: <Ynj5GZuXG6CgCUJp@hyeyoo>
References: <20220506045319.GA28237@DESKTOP-NK4TH6S.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220506045319.GA28237@DESKTOP-NK4TH6S.localdomain>
Precedence: bulk

On Fri, May 06, 2022 at 01:53:19PM +0900, Paran Lee wrote:
> Catch kmem_cache_alloc failed on slub kunit test.
> 
> Signed-off-by: Paran Lee <p4ranlee@gmail.com>
> ---
>  lib/slub_kunit.c | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/lib/slub_kunit.c b/lib/slub_kunit.c
> index 8662dc6cb509..7b80241dd498 100644
> --- a/lib/slub_kunit.c
> +++ b/lib/slub_kunit.c
> @@ -32,6 +32,11 @@ static void test_next_pointer(struct kunit *test)
>  	struct kmem_cache *s = kmem_cache_create("TestSlub_next_ptr_free", 64, 0,
>  				SLAB_POISON, NULL);
>  	u8 *p = kmem_cache_alloc(s, GFP_KERNEL);
> +	if (!p) {
> +		kunit_err(test, "Allocation failed: %s\n", __func__);
> +		kmem_cache_destroy(s);
> +		return;
> +	}
>  	unsigned long tmp;
>  	unsigned long *ptr_addr;
>  
> @@ -77,6 +82,11 @@ static void test_first_word(struct kunit *test)
>  	struct kmem_cache *s = kmem_cache_create("TestSlub_1th_word_free", 64, 0,
>  				SLAB_POISON, NULL);

Recently SLAB_NO_USER_FLAGS is added for test caches.
Looks like it's not based on Vlastimil's slab tree:
https://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git

>  	u8 *p = kmem_cache_alloc(s, GFP_KERNEL);
> +	if (!p) {
> +		kunit_err(test, "Allocation failed: %s\n", __func__);
> +		kmem_cache_destroy(s);
> +		return;
> +	}
>  
>  	kmem_cache_free(s, p);
>  	*p = 0x78;
> @@ -92,6 +102,11 @@ static void test_clobber_50th_byte(struct kunit *test)
>  	struct kmem_cache *s = kmem_cache_create("TestSlub_50th_word_free", 64, 0,
>  				SLAB_POISON, NULL);
>  	u8 *p = kmem_cache_alloc(s, GFP_KERNEL);
> +	if (!p) {
> +		kunit_err(test, "Allocation failed: %s\n", __func__);
> +		kmem_cache_destroy(s);
> +		return;
> +	}
>  
>  	kmem_cache_free(s, p);
>  	p[50] = 0x9a;
> @@ -108,6 +123,11 @@ static void test_clobber_redzone_free(struct kunit *test)
>  	struct kmem_cache *s = kmem_cache_create("TestSlub_RZ_free", 64, 0,
>  				SLAB_RED_ZONE, NULL);
>  	u8 *p = kmem_cache_alloc(s, GFP_KERNEL);
> +	if (!p) {
> +		kunit_err(test, "Allocation failed: %s\n", __func__);
> +		kmem_cache_destroy(s);
> +		return;
> +	}
>  
>  	kasan_disable_current();
>  	kmem_cache_free(s, p);
> -- 
> 2.25.1
> 

To be more paranoid kmem_cache_create() can also fail - but I'm not sure
these checks are useful for tests.

-- 
Thanks,
Hyeonggon