From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: Kees Cook <keescook@chromium.org>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: arm-linux-gnueabi-ld: section .rodata VMA overlaps section .bss VMA
Date: Sat, 11 Jul 2020 13:30:25 +0100 [thread overview]
Message-ID: <20200711123025.GM1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <202007111901.282t0ZCv%lkp@intel.com>
I doubt anyone is going to fix this; it's an XIP kernel, and it looks
like the .data and .rodata sections are correctly placed as per the
configuration, but for some reason the .text (and sections that follow)
are incorrectly placed in VMA space. The configuration file says that
the kernel should start at 0x00080000, and there's no way the .text
VMA should be starting at 0x3f0801a0.
Unless one of the XIP using folk can debug this, I doubt there will be
any movement on it. Especially as it's 5 months old...
What do we do with bugs like this that people won't fix? Remove XIP
support from the kernel?
On Sat, Jul 11, 2020 at 07:05:04PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 1df0d8960499e58963fd6c8ac75e544f2b417b29
> commit: f87b1c49bc675da30d8e1e8f4b60b800312c7b90 ARM: 8958/1: rename missed uaccess .fixup section
> date: 5 months ago
> config: arm-randconfig-c004-20200711 (attached as .config)
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
>
> 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 >>):
>
> arm-linux-gnueabi-ld: section .data VMA [0000000040008000,00000000401e9edf] overlaps section .text VMA [000000003f0801a0,0000000040515887]
> >> arm-linux-gnueabi-ld: section .rodata VMA [0000000040516000,00000000409a24ee] overlaps section .bss VMA [0000000040208000,00000000409d80db]
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-07-11 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 11:05 arm-linux-gnueabi-ld: section .rodata VMA overlaps section .bss VMA kernel test robot
2020-07-11 12:30 ` Russell King - ARM Linux admin [this message]
2020-07-11 14:59 ` Ard Biesheuvel
2020-07-11 16:03 ` Arnd Bergmann
2020-07-11 16:42 ` Ard Biesheuvel
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=20200711123025.GM1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.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