From: Thomas Gleixner <tglx@linutronix.de>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: 20241015061522.25288-1-rui.zhang@intel.com,
Zhang Rui <rui.zhang@intel.com>,
hpa@zytor.com, peterz@infradead.org, thorsten.blum@toblux.com,
yuntao.wang@linux.dev, tony.luck@intel.com, len.brown@intel.com,
srinivas.pandruvada@intel.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, rafael.j.wysocki@intel.com,
x86@kernel.org, linux-pm@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org
Subject: [PATCH] modpost: Add .irqentry.text to OTHER_SECTIONS
Date: Sun, 01 Dec 2024 12:17:30 +0100 [thread overview]
Message-ID: <87iks3wt2t.ffs@tglx> (raw)
In-Reply-To: <20241130114549.GI10431@google.com>
The compiler can fully inline the actual handler function of an interrupt
entry into the .irqentry.text entry point. If such a function contains an
access which has an exception table entry, modpost complains about a
section mismatch:
WARNING: vmlinux.o(__ex_table+0x447c): Section mismatch in reference ...
The relocation at __ex_table+0x447c references section ".irqentry.text"
which is not in the list of authorized sections.
Add .irqentry.text to OTHER_SECTIONS to cure the issue.
Reported-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: stable@vger.kernel.org
---
scripts/mod/modpost.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/scripts/mod/modpost.c
+++ b/scripts/mod/modpost.c
@@ -785,7 +785,7 @@ static void check_section(const char *mo
".ltext", ".ltext.*"
#define OTHER_TEXT_SECTIONS ".ref.text", ".head.text", ".spinlock.text", \
".fixup", ".entry.text", ".exception.text", \
- ".coldtext", ".softirqentry.text"
+ ".coldtext", ".softirqentry.text", ".irqentry.text"
#define ALL_TEXT_SECTIONS ".init.text", ".exit.text", \
TEXT_SECTIONS, OTHER_TEXT_SECTIONS
next prev parent reply other threads:[~2024-12-01 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 11:18 bisected: [PATCH V4] x86/apic: Always explicitly disarm TSC-deadline timer Sergey Senozhatsky
2024-11-28 11:22 ` Sergey Senozhatsky
2024-11-30 11:21 ` Thomas Gleixner
2024-11-30 11:45 ` Sergey Senozhatsky
2024-12-01 11:17 ` Thomas Gleixner [this message]
2024-12-02 2:02 ` [PATCH] modpost: Add .irqentry.text to OTHER_SECTIONS Masahiro Yamada
2024-12-02 21:03 ` Thomas Gleixner
2024-12-03 15:27 ` Masahiro Yamada
2024-12-03 16:10 ` Thomas Gleixner
2024-12-02 4:10 ` Sergey Senozhatsky
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=87iks3wt2t.ffs@tglx \
--to=tglx@linutronix.de \
--cc=20241015061522.25288-1-rui.zhang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--cc=senozhatsky@chromium.org \
--cc=srinivas.pandruvada@intel.com \
--cc=stable@vger.kernel.org \
--cc=thorsten.blum@toblux.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yuntao.wang@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).