From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [linux-next:master 7435/9209] include/linux/compiler_types.h:328:38: error: call to '__compiletime_assert_236' declared with attribute error: unexpected size in kmalloc_index()
Date: Sat, 12 Jun 2021 08:49:02 +0900 [thread overview]
Message-ID: <CAB=+i9SCouZTz8eFDgz4ahn-4OgYAhnE9PdzRA_gOLyV=99nPQ@mail.gmail.com> (raw)
In-Reply-To: <20210611161034.fde4e1bcffb92eaec061014b@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 3283 bytes --]
On Sat, Jun 12, 2021, 8:10 AM Andrew Morton <akpm@linux-foundation.org>
wrote:
> On Sat, 12 Jun 2021 00:08:43 +0800 kernel test robot <lkp@intel.com>
> wrote:
>
> > tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 25fe90f43fa312213b653dc1f12fd2d80f855883
> > commit: df2de13a32afec989c0e735beb3bc391b3de1dbd [7435/9209] mm, slub:
> change run-time assertion in kmalloc_index() to compile-time
> > config: sparc-randconfig-r005-20210611 (attached as .config)
> > compiler: sparc64-linux-gcc (GCC) 9.3.0
> > reproduce (this is a W=1 build):
> > wget
> https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross
> -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > #
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=df2de13a32afec989c0e735beb3bc391b3de1dbd
> > git remote add linux-next
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > git fetch --no-tags linux-next master
> > git checkout df2de13a32afec989c0e735beb3bc391b3de1dbd
> > # save the attached .config to linux build tree
> > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross
> ARCH=sparc
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> > All errors (new ones prefixed by >>):
> >
> > In file included from <command-line>:
> > In function 'kmalloc_index',
> > inlined from 'kmalloc_node' at include/linux/slab.h:572:20,
> > inlined from 'bpf_map_kmalloc_node.isra.0.part.0' at
> include/linux/bpf.h:1319:9:
> > >> include/linux/compiler_types.h:328:38: error: call to
> '__compiletime_assert_236' declared with attribute error: unexpected size
> in kmalloc_index()
> > 328 | _compiletime_assert(condition, msg, __compiletime_assert_,
> __COUNTER__)
> > | ^
> > include/linux/compiler_types.h:309:4: note: in definition of macro
> '__compiletime_assert'
> > 309 | prefix ## suffix(); \
> > | ^~~~~~
> > include/linux/compiler_types.h:328:2: note: in expansion of macro
> '_compiletime_assert'
> > 328 | _compiletime_assert(condition, msg, __compiletime_assert_,
> __COUNTER__)
> > | ^~~~~~~~~~~~~~~~~~~
> > include/linux/build_bug.h:39:37: note: in expansion of macro
> 'compiletime_assert'
> > 39 | #define BUILD_BUG_ON_MSG(cond, msg)
> compiletime_assert(!(cond), msg)
> > | ^~~~~~~~~~~~~~~~~~
> > include/linux/slab.h:389:2: note: in expansion of macro
> 'BUILD_BUG_ON_MSG'
> > 389 | BUILD_BUG_ON_MSG(1, "unexpected size in kmalloc_index()");
> > | ^~~~~~~~~~~~~~~~
> >
>
> This log doesn't show which .c file was being compiled at the time.
> Can this info be included?
>
> For me, it was kernel/bpf/local_storage.c.
>
Yes. the file It is kernel/bpf/local_storage.c
>
> I don't see anything wrong with the code. Did this gcc simply screw up
> __builtin_constant_p()?
It seems there is false positive when CONFIG_PROFILE_ALL_BRANCHES=y
See this:
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org/thread/45UNTPJX7VUKLB6TUYPJOS7DMREVW5US/
[-- Attachment #2: Type: text/html, Size: 5439 bytes --]
prev parent reply other threads:[~2021-06-11 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 16:08 kernel test robot
2021-06-11 23:10 ` Andrew Morton
2021-06-11 23:49 ` Hyeonggon Yoo [this message]
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='CAB=+i9SCouZTz8eFDgz4ahn-4OgYAhnE9PdzRA_gOLyV=99nPQ@mail.gmail.com' \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=vbabka@suse.cz \
/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