From: Vlastimil Babka <vbabka@suse.cz>
To: Baoquan He <bhe@redhat.com>, kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Dennis Zhou <dennis@kernel.org>,
42.hyeyoo@gmail.com
Subject: Re: [linux-next:master 5002/7443] include/linux/compiler_types.h:357:45: error: call to '__compiletime_assert_474' declared with attribute error: BUILD_BUG_ON failed: PERCPU_DYNAMIC_EARLY_SIZE < NR_KMALLOC_TYPES * KMALLOC_SHIFT_HIGH * sizeof(struct kmem_cache_cpu)
Date: Mon, 14 Nov 2022 18:58:13 +0100 [thread overview]
Message-ID: <dda9e5fc-258b-bf67-c90a-f7fb23ab68e3@suse.cz> (raw)
In-Reply-To: <Y3Hx8SYyD9y1Q8o/@MiWiFi-R3L-srv>
On 11/14/22 08:44, Baoquan He wrote:
> Hi,
>
> I reproduced the build failure according to lkp report and made a patch
> as below to fix it.
>
> From dae7dd9705015ce36db757e88c78802584f949b1 Mon Sep 17 00:00:00 2001
> From: Baoquan He <bhe@redhat.com>
> Date: Sun, 13 Nov 2022 18:08:27 +0800
> Subject: [PATCH] percpu: adjust the value of PERCPU_DYNAMIC_EARLY_SIZE
> Content-type: text/plain
>
> LKP reported a build failure as below on the patch "mm/slub, percpu:
> correct the calculation of early percpu allocation size"
Since I have that patch in slab.git exposed to -next, should I take this fix
too, to make things simpler? Dennis?
> ~~~~~~
> In file included from <command-line>:
> In function 'alloc_kmem_cache_cpus',
> inlined from 'kmem_cache_open' at mm/slub.c:4340:6:
>>> include/linux/compiler_types.h:357:45: error: call to '__compiletime_assert_474' declared with attribute error:
> BUILD_BUG_ON failed: PERCPU_DYNAMIC_EARLY_SIZE < NR_KMALLOC_TYPES * KMALLOC_SHIFT_HIGH * sizeof(struct kmem_cache_cpu)
> 357 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
> ~~~~~~
>
> From the kernel config file provided by LKP, the building was made on
> arm64 with below Kconfig item enabled:
>
> CONFIG_ZONE_DMA=y
> CONFIG_SLUB_CPU_PARTIAL=y
> CONFIG_DEBUG_LOCK_ALLOC=y
> CONFIG_SLUB_STATS=y
> CONFIG_ARM64_PAGE_SHIFT=16
> CONFIG_ARM64_64K_PAGES=y
>
> Then we will have:
> NR_KMALLOC_TYPES:4
> KMALLOC_SHIFT_HIGH:17
> sizeof(struct kmem_cache_cpu):184
>
> The product of them is 12512, which is bigger than PERCPU_DYNAMIC_EARLY_SIZE,
> 12K. Hence, the BUILD_BUG_ON in alloc_kmem_cache_cpus() is triggered.
>
> Earlier, in commit 099a19d91ca4 ("percpu: allow limited allocation
> before slab is online"), PERCPU_DYNAMIC_EARLY_SIZE was introduced and
> set to 12K which is equal to the then PERPCU_DYNAMIC_RESERVE.
> Later, in commit 1a4d76076cda ("percpu: implement asynchronous chunk
> population"), PERPCU_DYNAMIC_RESERVE was increased by 8K, while
> PERCPU_DYNAMIC_EARLY_SIZE was kept unchanged.
>
> So, here increase PERCPU_DYNAMIC_EARLY_SIZE by 8K too to accommodate to
> the slub's requirement.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Baoquan He <bhe@redhat.com>
> ---
> include/linux/percpu.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/percpu.h b/include/linux/percpu.h
> index 70bc17db00a6..1338ea2aa720 100644
> --- a/include/linux/percpu.h
> +++ b/include/linux/percpu.h
> @@ -41,7 +41,7 @@
> * for this. Keep PERCPU_DYNAMIC_RESERVE equal to or larger than
> * PERCPU_DYNAMIC_EARLY_SIZE.
> */
> -#define PERCPU_DYNAMIC_EARLY_SIZE (12 << 10)
> +#define PERCPU_DYNAMIC_EARLY_SIZE (20 << 10)
>
> /*
> * PERCPU_DYNAMIC_RESERVE indicates the amount of free area to piggy
next prev parent reply other threads:[~2022-11-14 17:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 20:15 [linux-next:master 5002/7443] include/linux/compiler_types.h:357:45: error: call to '__compiletime_assert_474' declared with attribute error: BUILD_BUG_ON failed: PERCPU_DYNAMIC_EARLY_SIZE < NR_KMALLOC_TYPES * KMALLOC_SHIFT_HIGH * sizeof(struct kmem_cache_cpu) kernel test robot
2022-11-12 0:45 ` Baoquan He
2022-11-14 7:44 ` Baoquan He
2022-11-14 17:58 ` Vlastimil Babka [this message]
2022-11-15 4:13 ` Dennis Zhou
2022-11-15 9:08 ` Baoquan He
2022-11-15 20:00 ` Dennis Zhou
2022-11-16 11:32 ` Baoquan He
2022-11-17 19:23 ` Dennis Zhou
2022-11-18 3:40 ` Baoquan He
2022-11-18 9:49 ` Vlastimil Babka
2022-11-18 19:08 ` Dennis Zhou
2022-11-21 9:22 ` Vlastimil Babka
2022-11-16 12:49 ` Hyeonggon Yoo
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=dda9e5fc-258b-bf67-c90a-f7fb23ab68e3@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=bhe@redhat.com \
--cc=dennis@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).