From: Thomas Gleixner <tglx@linutronix.de>
To: kernel test robot <lkp@intel.com>, x86-ml <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [tip:irq/urgent] BUILD REGRESSION 9f7488f24c7571d349d938061e0ede7a39b65d6b
Date: Thu, 07 Aug 2025 11:00:38 +0200 [thread overview]
Message-ID: <87h5yjcxqh.ffs@tglx> (raw)
In-Reply-To: <202508071514.CFNi6mo5-lkp@intel.com>
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
next parent reply other threads:[~2025-08-07 9:00 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 ` Thomas Gleixner [this message]
2025-08-07 11:48 ` [tip:irq/urgent] BUILD REGRESSION 9f7488f24c7571d349d938061e0ede7a39b65d6b Alexandre Ghiti
2025-08-08 1:28 ` Philip Li
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=87h5yjcxqh.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--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