* Re: [tip:irq/urgent] BUILD REGRESSION 9f7488f24c7571d349d938061e0ede7a39b65d6b
[not found] <202508071514.CFNi6mo5-lkp@intel.com>
@ 2025-08-07 9:00 ` Thomas Gleixner
2025-08-07 11:48 ` Alexandre Ghiti
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Gleixner @ 2025-08-07 9:00 UTC (permalink / raw)
To: kernel test robot, x86-ml; +Cc: linux-kernel, linux-riscv
On Thu, Aug 07 2025 at 15:10, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/urgent
> branch HEAD: 9f7488f24c7571d349d938061e0ede7a39b65d6b irqchip/mvebu-gicp: Use resource_size() for ioremap()
>
> Error/Warning (recently discovered and may have been fixed):
>
> https://lore.kernel.org/oe-kbuild-all/202508070607.QKVa8DiU-lkp@intel.com
>
> ERROR: modpost: __ex_table+0x1584 references non-executable section '.rodata.__func__.103779'
>
> Error/Warning ids grouped by kconfigs:
>
> recent_errors
> `-- riscv-randconfig-002-20250807
> `-- ERROR:__ex_table-references-non-executable-section-.rodata.__func__.
This has nothing to do with the above commit. That's just a new one
of the same type as the ones which existed before:
WARNING: modpost: vmlinux: section mismatch in reference: xp_fill_cb+0x46 (section: .text.xp_fill_cb) -> .L62 (section: .init.text)
...
WARNING: modpost: vmlinux: section mismatch in reference: 0x19e4 (section: __ex_table) -> .LASF400 (section: .debug_str)
There are gazillions of them and that's a purely riscv specific related
problem.
Thanks,
tglx
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [tip:irq/urgent] BUILD REGRESSION 9f7488f24c7571d349d938061e0ede7a39b65d6b
2025-08-07 9:00 ` [tip:irq/urgent] BUILD REGRESSION 9f7488f24c7571d349d938061e0ede7a39b65d6b Thomas Gleixner
@ 2025-08-07 11:48 ` Alexandre Ghiti
2025-08-08 1:28 ` Philip Li
0 siblings, 1 reply; 3+ messages in thread
From: Alexandre Ghiti @ 2025-08-07 11:48 UTC (permalink / raw)
To: Thomas Gleixner, kernel test robot, x86-ml, Marco Bonelli
Cc: linux-kernel, linux-riscv
On 8/7/25 11:00, Thomas Gleixner wrote:
> On Thu, Aug 07 2025 at 15:10, kernel test robot wrote:
>> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/urgent
>> branch HEAD: 9f7488f24c7571d349d938061e0ede7a39b65d6b irqchip/mvebu-gicp: Use resource_size() for ioremap()
>>
>> Error/Warning (recently discovered and may have been fixed):
>>
>> https://lore.kernel.org/oe-kbuild-all/202508070607.QKVa8DiU-lkp@intel.com
>>
>> ERROR: modpost: __ex_table+0x1584 references non-executable section '.rodata.__func__.103779'
>>
>> Error/Warning ids grouped by kconfigs:
>>
>> recent_errors
>> `-- riscv-randconfig-002-20250807
>> `-- ERROR:__ex_table-references-non-executable-section-.rodata.__func__.
> This has nothing to do with the above commit. That's just a new one
> of the same type as the ones which existed before:
>
> WARNING: modpost: vmlinux: section mismatch in reference: xp_fill_cb+0x46 (section: .text.xp_fill_cb) -> .L62 (section: .init.text)
> ...
> WARNING: modpost: vmlinux: section mismatch in reference: 0x19e4 (section: __ex_table) -> .LASF400 (section: .debug_str)
>
> There are gazillions of them and that's a purely riscv specific related
> problem.
Yes that's a riscv issue that was already reported by Marco [1] who also
found the underlying issue [2]. The problem is that we emit too many
relocations which overflow the number of possible relocations in 32-bit.
After discussion with some riscv gcc folks, it appears to be caused by
relaxations which, according to the ABI, require the emission of local
symbol. We don't have a workaround for now and we'll discuss this issue
with the ABI authors.
[1]
https://lore.kernel.org/linux-riscv/960240908.630790.1748641210849@privateemail.com/
[2]
https://lore.kernel.org/all/1714337938.319508.1750244108368@privateemail.com/
Sorry for the noise,
Alex
>
> Thanks,
>
> tglx
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [tip:irq/urgent] BUILD REGRESSION 9f7488f24c7571d349d938061e0ede7a39b65d6b
2025-08-07 11:48 ` Alexandre Ghiti
@ 2025-08-08 1:28 ` Philip Li
0 siblings, 0 replies; 3+ messages in thread
From: Philip Li @ 2025-08-08 1:28 UTC (permalink / raw)
To: Alexandre Ghiti
Cc: Thomas Gleixner, kernel test robot, x86-ml, Marco Bonelli,
linux-kernel, linux-riscv
On Thu, Aug 07, 2025 at 01:48:25PM +0200, Alexandre Ghiti wrote:
> On 8/7/25 11:00, Thomas Gleixner wrote:
> > On Thu, Aug 07 2025 at 15:10, kernel test robot wrote:
> > > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/urgent
> > > branch HEAD: 9f7488f24c7571d349d938061e0ede7a39b65d6b irqchip/mvebu-gicp: Use resource_size() for ioremap()
> > >
> > > Error/Warning (recently discovered and may have been fixed):
> > >
> > > https://lore.kernel.org/oe-kbuild-all/202508070607.QKVa8DiU-lkp@intel.com
> > >
> > > ERROR: modpost: __ex_table+0x1584 references non-executable section '.rodata.__func__.103779'
> > >
> > > Error/Warning ids grouped by kconfigs:
> > >
> > > recent_errors
> > > `-- riscv-randconfig-002-20250807
> > > `-- ERROR:__ex_table-references-non-executable-section-.rodata.__func__.
> > This has nothing to do with the above commit. That's just a new one
> > of the same type as the ones which existed before:
> >
> > WARNING: modpost: vmlinux: section mismatch in reference: xp_fill_cb+0x46 (section: .text.xp_fill_cb) -> .L62 (section: .init.text)
> > ...
> > WARNING: modpost: vmlinux: section mismatch in reference: 0x19e4 (section: __ex_table) -> .LASF400 (section: .debug_str)
> >
> > There are gazillions of them and that's a purely riscv specific related
> > problem.
>
>
> Yes that's a riscv issue that was already reported by Marco [1] who also
> found the underlying issue [2]. The problem is that we emit too many
> relocations which overflow the number of possible relocations in 32-bit.
> After discussion with some riscv gcc folks, it appears to be caused by
> relaxations which, according to the ABI, require the emission of local
> symbol. We don't have a workaround for now and we'll discuss this issue with
> the ABI authors.
Sorry for multiple confusing reports from the bot, I will disable the further report
of this is riscv issue.
>
> [1] https://lore.kernel.org/linux-riscv/960240908.630790.1748641210849@privateemail.com/
> [2]
> https://lore.kernel.org/all/1714337938.319508.1750244108368@privateemail.com/
>
> Sorry for the noise,
>
> Alex
>
>
> >
> > Thanks,
> >
> > tglx
> >
> > _______________________________________________
> > linux-riscv mailing list
> > linux-riscv@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-riscv
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-08-08 1:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <202508071514.CFNi6mo5-lkp@intel.com>
2025-08-07 9:00 ` [tip:irq/urgent] BUILD REGRESSION 9f7488f24c7571d349d938061e0ede7a39b65d6b Thomas Gleixner
2025-08-07 11:48 ` Alexandre Ghiti
2025-08-08 1:28 ` Philip Li
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).