linux-kernel - Re: arm-linux-gnueabi-ld: section .rodata VMA overlaps section .bss VMA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 11 Jul 2020 17:59:59 +0300
From:   Ard Biesheuvel <ardb@...nel.org>
To:     Russell King - ARM Linux admin <linux@...linux.org.uk>,
        Arnd Bergmann <arnd@...db.de>
Cc:     kernel test robot <lkp@...el.com>,
        Kees Cook <keescook@...omium.org>, kbuild-all@...ts.01.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: arm-linux-gnueabi-ld: section .rodata VMA overlaps section .bss VMA

(+ Arnd)

On Sat, 11 Jul 2020 at 15:30, Russell King - ARM Linux admin
<linux@...linux.org.uk> wrote:
>
> 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.
>

Note that only one of those lines has the >> prefix, and so this
config was broken even before this patch got applied.

> 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?
>

I fail to see the point of randconfig testing for xip kernels tbh, and
i don't think it is fair to disable xip altogether if the configs that
those people care about still build as expected.

But it would indeed be nice if we could at least get rid of these
pointless build reports. Is there any way we can avoid xip from being
selected by randconfig?


> 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@...el.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!