From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kbuild test robot <lkp@intel.com>, Max Filippov <jcmvbkbc@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: WARNING: lib/test_bitmap.o(.text.unlikely+0x5c): Section mismatch in reference from the function bitmap_copy_clear_tail() to the variable .init.rodata:clump_exp
Date: Fri, 13 Dec 2019 13:16:49 +0200 [thread overview]
Message-ID: <20191213111649.GU32742@smile.fi.intel.com> (raw)
In-Reply-To: <201912100401.fDYi5lhU%lkp@intel.com>
On Tue, Dec 10, 2019 at 04:17:03AM +0800, kbuild test robot wrote:
+Cc: Max for xtensa matters, perhaps he has an idea.
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: e42617b825f8073569da76dc4510bfa019b1c35a
> commit: 30544ed5de431fe25d3793e4dd5a058d877c4d77 lib/bitmap: introduce bitmap_replace() helper
> date: 5 days ago
> config: xtensa-randconfig-a001-20191209 (attached as .config)
> compiler: xtensa-linux-gcc (GCC) 7.5.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 30544ed5de431fe25d3793e4dd5a058d877c4d77
> # save the attached .config to linux build tree
> GCC_VERSION=7.5.0 make.cross ARCH=xtensa
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
I'm not sure I got this (esp. relation to my patch).
The mentioned code definitely compiled for 32-bit (since only then mentioned
bitmap API is in use). I have tried to reproduce on i386 compilation (gcc 9.x),
but can't.
> >> WARNING: lib/test_bitmap.o(.text.unlikely+0x5c): Section mismatch in reference from the function bitmap_copy_clear_tail() to the variable .init.rodata:clump_exp
> The function bitmap_copy_clear_tail() references
> the variable __initconst clump_exp.
> This is often because bitmap_copy_clear_tail lacks a __initconst
> annotation or the annotation of clump_exp is wrong.
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-12-13 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 20:17 kbuild test robot
2019-12-13 11:16 ` Andy Shevchenko [this message]
2019-12-13 21:08 ` Max Filippov
2019-12-13 21:19 ` Andy Shevchenko
2019-12-15 3:17 ` Max Filippov
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=20191213111649.GU32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=jcmvbkbc@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
/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