From: Philip Li <philip.li@intel.com>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: Thomas Gleixner <tglx@linutronix.de>,
kernel test robot <lkp@intel.com>, x86-ml <x86@kernel.org>,
Marco Bonelli <marco@mebeim.net>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [tip:irq/urgent] BUILD REGRESSION 9f7488f24c7571d349d938061e0ede7a39b65d6b
Date: Fri, 8 Aug 2025 09:28:22 +0800 [thread overview]
Message-ID: <aJVStgD9ML6ykdXS@rli9-mobl> (raw)
In-Reply-To: <d5e49344-e0c2-4095-bd1f-d2d23a8e6534@ghiti.fr>
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
prev parent reply other threads:[~2025-08-08 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 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=aJVStgD9ML6ykdXS@rli9-mobl \
--to=philip.li@intel.com \
--cc=alex@ghiti.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=marco@mebeim.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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