From: "Liu, Yujie" <yujie.liu@intel.com>
To: "andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>, lkp <lkp@intel.com>
Cc: "glider@google.com" <glider@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"yury.norov@gmail.com" <yury.norov@gmail.com>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"Lobakin, Aleksander" <aleksander.lobakin@intel.com>
Subject: Re: [linux-next:master 2203/5042] WARNING: modpost: vmlinux: section mismatch in reference: bitmap_read+0x128 (section: .text.unlikely) -> __setup_str_initcall_blacklist (section: .init.rodata)
Date: Thu, 11 Apr 2024 09:48:29 +0000 [thread overview]
Message-ID: <8aaf29b84843289c2c1652df7e4fe158a6e2628d.camel@intel.com> (raw)
In-Reply-To: <Zhav9krPj3qBjpuP@smile.fi.intel.com>
Hi Andy,
On Wed, 2024-04-10 at 18:27 +0300, Andy Shevchenko wrote:
> On Wed, Apr 10, 2024 at 11:22:16PM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 6ebf211bb11dfc004a2ff73a9de5386fa309c430
> > commit: 991e5583647d33ee3a9c89248974ef98b9f539a8 [2203/5042] lib/test_bitmap: add tests for bitmap_{read,write}()
> > config: xtensa-randconfig-r012-20230725 (https://download.01.org/0day-ci/archive/20240410/202404102353.Cv1gUjk3-lkp@intel.com/config)
> > compiler: xtensa-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240410/202404102353.Cv1gUjk3-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > > Reported-by: kernel test robot <lkp@intel.com>
> > > Closes: https://lore.kernel.org/oe-kbuild-all/202404102353.Cv1gUjk3-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> >
> > WARNING: modpost: missing MODULE_DESCRIPTION() in vmlinux.o
> > > > WARNING: modpost: vmlinux: section mismatch in reference: bitmap_read+0x128 (section: .text.unlikely) -> __setup_str_initcall_blacklist (section: .init.rodata)
> > WARNING: modpost: vmlinux: section mismatch in reference: bitmap_allocate_region+0xb4 (section: .text.unlikely) -> __setup_str_initcall_blacklist (section: .init.rodata)
>
> As pointed out earlier, this is unconfirmed bug in GCC (GCC developers
> point a finger at kernel code and vice versa). Can you reproduce this
> with clang?
Thanks for the reminder of the previous comment in [1].
[1] https://lore.kernel.org/all/202403121032.WDY8ftKq-lkp@intel.com/
This warning was captured in a randconfig cross compilation for xtensa
architecture. Seems clang doesn't support xtensa backend yet. We tried
some randconfig build for x86_64 with clang, but cannot reproduce
this.
We only observed this warning on xtensa, but not on other
architectures, so we don't have other configs at hand that can be used
to reproduce with clang. Sorry for this.
--
Best Regards,
Yujie
prev parent reply other threads:[~2024-04-11 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 15:22 kernel test robot
2024-04-10 15:27 ` Andy Shevchenko
2024-04-11 9:08 ` Alexander Lobakin
2024-04-11 9:29 ` Andy Shevchenko
2024-04-11 9:48 ` Liu, Yujie [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=8aaf29b84843289c2c1652df7e4fe158a6e2628d.camel@intel.com \
--to=yujie.liu@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=glider@google.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yury.norov@gmail.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