From: Paul Moore <paul@paul-moore.com>
To: Feng Tang <feng.tang@intel.com>
Cc: lkp <lkp@intel.com>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [linux-next:master 5983/6048] h8300-linux-ld: section .data VMA overlaps section __kcrctab VMA
Date: Mon, 1 Mar 2021 09:40:29 -0500 [thread overview]
Message-ID: <CAHC9VhT9Mzocw3w6JfHbvqm4=7wWodbrdAA4BoOU2VqGHavZBQ@mail.gmail.com> (raw)
In-Reply-To: <20210301060822.GA21746@shbuild999.sh.intel.com>
On Mon, Mar 1, 2021 at 1:08 AM Feng Tang <feng.tang@intel.com> wrote:
>
> Hi Paul,
>
> On Wed, Feb 10, 2021 at 02:21:41AM +0800, Paul Moore wrote:
> > On Tue, Feb 9, 2021 at 1:09 PM kernel test robot <lkp@intel.com> wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > > head: 59fa6a163ffabc1bf25c5e0e33899e268a96d3cc
> > > commit: 77d8143a5290b38e3331f61f55c0b682699884bc [5983/6048] Merge remote-tracking branch 'selinux/next'
> > > config: h8300-randconfig-r005-20210209 (attached as .config)
> > > compiler: h8300-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=77d8143a5290b38e3331f61f55c0b682699884bc
> > > 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 77d8143a5290b38e3331f61f55c0b682699884bc
> > > # save the attached .config to linux build tree
> > > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300
> > >
> > > 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 >>):
> > >
> > > h8300-linux-ld: section .init.text LMA [0000000000430360,00000000004479a1] overlaps section .data LMA [000000000041868c,00000000004489eb]
> > > >> h8300-linux-ld: section .data VMA [0000000000400000,000000000043035f] overlaps section __kcrctab VMA [00000000003fdd74,000000000040007b]
> > > >> h8300-linux-ld: section __kcrctab_gpl VMA [000000000040007c,00000000004025a7] overlaps section .data VMA [0000000000400000,000000000043035f]
> > > h8300-linux-ld: arch/h8300/kernel/entry.o: in function `resume_kernel':
> > > (.text+0x29a): undefined reference to `TI_PRE_COUNT'
> >
> > This really doesn't look like something caused by SELinux ...
>
> No, this is not related with SELinux, sorry for the false alarm.
Thanks for confirming this and providing an explanation of the root cause.
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2021-03-01 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 18:09 [linux-next:master 5983/6048] h8300-linux-ld: section .data VMA overlaps section __kcrctab VMA kernel test robot
2021-02-09 18:21 ` Paul Moore
2021-02-10 6:33 ` Rong Chen
2021-03-01 6:08 ` Feng Tang
2021-03-01 14:40 ` Paul Moore [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='CAHC9VhT9Mzocw3w6JfHbvqm4=7wWodbrdAA4BoOU2VqGHavZBQ@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=feng.tang@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
/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).