From: Luis Chamberlain <mcgrof@kernel.org>
To: masahiroy@kernel.org, deller@gmx.de
Cc: mcgrof@kernel.org, arnd@arndb.de, linux-arch@vger.kernel.org,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 4/4] modules: Add missing entry for __ex_table
Date: Mon, 29 Jan 2024 11:26:43 -0800 [thread overview]
Message-ID: <20240129192644.3359978-5-mcgrof@kernel.org> (raw)
In-Reply-To: <20240129192644.3359978-1-mcgrof@kernel.org>
From: Helge Deller <deller@gmx.de>
The entry for __ex_table was missing, which may make __ex_table
become 1- or 2-byte aligned in modules.
Add the entry to ensure it gets 32-bit aligned.
Signed-off-by: Helge Deller <deller@gmx.de>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
scripts/module.lds.S | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/module.lds.S b/scripts/module.lds.S
index b00415a9ff27..488f61b156b2 100644
--- a/scripts/module.lds.S
+++ b/scripts/module.lds.S
@@ -26,6 +26,7 @@ SECTIONS {
.altinstructions 0 : ALIGN(8) { KEEP(*(.altinstructions)) }
__bug_table 0 : ALIGN(8) { KEEP(*(__bug_table)) }
__jump_table 0 : ALIGN(8) { KEEP(*(__jump_table)) }
+ __ex_table 0 : ALIGN(4) { KEEP(*(__ex_table)) }
__patchable_function_entries : { *(__patchable_function_entries) }
--
2.42.0
next prev parent reply other threads:[~2024-01-29 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 19:26 [PATCH v2 0/3] modules: few of alignment fixes Luis Chamberlain
2024-01-29 19:26 ` [PATCH v2 1/4] selftests: add new kallsyms selftests Luis Chamberlain
2024-01-29 19:26 ` [PATCH v2 2/4] modules: Ensure 64-bit alignment on __ksymtab_* sections Luis Chamberlain
2024-01-29 19:26 ` [PATCH v2 3/4] vmlinux.lds.h: add missing alignment for symbol CRCs Luis Chamberlain
2024-01-29 19:26 ` Luis Chamberlain [this message]
2024-01-31 22:11 ` [PATCH v2 0/3] modules: few of alignment fixes Luis Chamberlain
2024-02-01 18:05 ` Luis Chamberlain
2024-02-02 15:20 ` Masahiro Yamada
2024-02-02 18:23 ` Luis Chamberlain
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=20240129192644.3359978-5-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=arnd@arndb.de \
--cc=deller@gmx.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=masahiroy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.