From: "Liu, Yujie" <yujie.liu@intel.com>
To: lkp <lkp@intel.com>, "vbabka@suse.cz" <vbabka@suse.cz>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>
Subject: Re: [linux-next:master 3501/3504] riscv32-linux-ld: section .data LMA [001f9000,009465d7] overlaps section .text LMA [000a7e84,0177d68b]
Date: Sun, 7 Apr 2024 06:28:47 +0000 [thread overview]
Message-ID: <3bbb804fac10a2d3ddd579414bb2246bf73665ce.camel@intel.com> (raw)
In-Reply-To: <7fa6ba05-44a3-456c-a2cd-35f4b02138c4@suse.cz>
On Thu, 2024-04-04 at 10:13 +0200, Vlastimil Babka wrote:
> On 4/3/24 3:34 PM, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 727900b675b749c40ba1f6669c7ae5eb7eb8e837
> > commit: 68cd017e43dd5657fd2875b38da5933e1fa7660c [3501/3504] Merge branch 'slab/for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git
> > config: riscv-randconfig-r032-20221115 (https://download.01.org/0day-ci/archive/20240403/202404032101.sKzRXCWH-lkp@intel.com/config)
> > compiler: riscv32-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240403/202404032101.sKzRXCWH-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/202404032101.sKzRXCWH-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > > > riscv32-linux-ld: section .data LMA [001f9000,009465d7] overlaps section .text LMA [000a7e84,0177d68b]
> > riscv32-linux-ld: section .pci_fixup VMA [c2167be0,c216a82f] overlaps section .data VMA [c2000000,c274d5d7]
>
> Hm I don't really see how the slab/for-next could cause this. Could it be
> false positive?
We looked into this case and found that the bot wrongly parsed the
riscv linker error and triggered a wrong bisection. We will fix the bug
at the bot side as soon as possible. Please kindly ignore this report
and the report at [1]. Sorry for the noise.
[1] https://lore.kernel.org/oe-kbuild-all/202404052022.Cwf2ilBp-lkp@intel.com/
Thanks,
Yujie
prev parent reply other threads:[~2024-04-07 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 13:34 kernel test robot
2024-04-04 8:13 ` Vlastimil Babka
2024-04-07 6:28 ` 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=3bbb804fac10a2d3ddd579414bb2246bf73665ce.camel@intel.com \
--to=yujie.liu@intel.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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