9:05 p.m.
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(a)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
10:30 p.m.
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(a)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!
12:59 a.m.
(+ Arnd)
On Sat, 11 Jul 2020 at 15:30, Russell King - ARM Linux admin
<linux(a)armlinux.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(a)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!
2:03 a.m.
On Sat, Jul 11, 2020 at 5:00 PM Ard Biesheuvel <ardb(a)kernel.org> wrote:
On Sat, 11 Jul 2020 at 15:30, Russell King - ARM Linux admin
<linux(a)armlinux.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?
In my randconfig builds, I have a patch that makes CONFIG_XIP_KERNEL
and some other options depend on '!COMPILE_TEST', and I always enable
COMPILE_TEST for randconfig builds. I don't know whether that would
work for the kernel test robot as well.
Arnd
2:42 a.m.
On Sat, 11 Jul 2020 at 19:03, Arnd Bergmann <arnd(a)arndb.de> wrote:
On Sat, Jul 11, 2020 at 5:00 PM Ard Biesheuvel <ardb(a)kernel.org> wrote:
> On Sat, 11 Jul 2020 at 15:30, Russell King - ARM Linux admin
> <linux(a)armlinux.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?
In my randconfig builds, I have a patch that makes CONFIG_XIP_KERNEL
and some other options depend on '!COMPILE_TEST', and I always enable
COMPILE_TEST for randconfig builds. I don't know whether that would
work for the kernel test robot as well.
Both changes sound like things we might simply upstream, no?
Randconfig is only intended for compile testing anyway, and making xip
depend on !COMPILE_TEST seems uncontroversial to me as well.
801
days inactive
801
days old
4 comments
4 participants
participants (4)
-
Ard Biesheuvel -
Arnd Bergmann -
kernel test robot -
Russell King - ARM Linux admin