From: Christophe Leroy <christophe.leroy@csgroup.eu> To: Luis Chamberlain <mcgrof@kernel.org>, Jessica Yu <jeyu@kernel.org> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>, "kgdb-bugreport@lists.sourceforge.net" <kgdb-bugreport@lists.sourceforge.net>, "linux-mm@kvack.org" <linux-mm@kvack.org>, "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org> Subject: [PATCH v2 0/5] Allocate module text and data separately Date: Thu, 27 Jan 2022 11:27:56 +0000 [thread overview] Message-ID: <cover.1643282353.git.christophe.leroy@csgroup.eu> (raw) This series allow architectures to request having modules data in vmalloc area instead of module area. This is required on powerpc book3s/32 in order to set data non executable, because it is not possible to set executability on page basis, this is done per 256 Mbytes segments. The module area has exec right, vmalloc area has noexec. Without this change module data remains executable regardless of CONFIG_STRICT_MODULES_RWX. This can also be useful on other powerpc/32 in order to maximize the chance of code being close enough to kernel core to avoid branch trampolines. Changes in v2: - Dropped first two patches which are not necessary. They may be added back later as a follow-up series. - Fixed the printks in GDB Christophe Leroy (5): modules: Always have struct mod_tree_root modules: Prepare for handling several RB trees modules: Introduce data_layout modules: Add CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC powerpc: Select ARCH_WANTS_MODULES_DATA_IN_VMALLOC on book3s/32 and 8xx arch/Kconfig | 6 ++ arch/powerpc/Kconfig | 1 + include/linux/module.h | 8 ++ kernel/debug/kdb/kdb_main.c | 10 +- kernel/module.c | 193 +++++++++++++++++++++++++----------- 5 files changed, 156 insertions(+), 62 deletions(-) -- 2.33.1
WARNING: multiple messages have this Message-ID (diff)
From: Christophe Leroy <christophe.leroy@csgroup.eu> To: Luis Chamberlain <mcgrof@kernel.org>, Jessica Yu <jeyu@kernel.org> Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>, "kgdb-bugreport@lists.sourceforge.net" <kgdb-bugreport@lists.sourceforge.net>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-mm@kvack.org" <linux-mm@kvack.org>, "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org> Subject: [PATCH v2 0/5] Allocate module text and data separately Date: Thu, 27 Jan 2022 11:27:56 +0000 [thread overview] Message-ID: <cover.1643282353.git.christophe.leroy@csgroup.eu> (raw) This series allow architectures to request having modules data in vmalloc area instead of module area. This is required on powerpc book3s/32 in order to set data non executable, because it is not possible to set executability on page basis, this is done per 256 Mbytes segments. The module area has exec right, vmalloc area has noexec. Without this change module data remains executable regardless of CONFIG_STRICT_MODULES_RWX. This can also be useful on other powerpc/32 in order to maximize the chance of code being close enough to kernel core to avoid branch trampolines. Changes in v2: - Dropped first two patches which are not necessary. They may be added back later as a follow-up series. - Fixed the printks in GDB Christophe Leroy (5): modules: Always have struct mod_tree_root modules: Prepare for handling several RB trees modules: Introduce data_layout modules: Add CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC powerpc: Select ARCH_WANTS_MODULES_DATA_IN_VMALLOC on book3s/32 and 8xx arch/Kconfig | 6 ++ arch/powerpc/Kconfig | 1 + include/linux/module.h | 8 ++ kernel/debug/kdb/kdb_main.c | 10 +- kernel/module.c | 193 +++++++++++++++++++++++++----------- 5 files changed, 156 insertions(+), 62 deletions(-) -- 2.33.1
next reply other threads:[~2022-01-27 11:28 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-27 11:27 Christophe Leroy [this message] 2022-01-27 11:27 ` [PATCH v2 0/5] Allocate module text and data separately Christophe Leroy 2022-01-27 11:27 ` [PATCH v2 1/5] modules: Always have struct mod_tree_root Christophe Leroy 2022-01-27 11:27 ` Christophe Leroy 2022-01-27 11:28 ` [PATCH v2 2/5] modules: Prepare for handling several RB trees Christophe Leroy 2022-01-27 11:28 ` Christophe Leroy 2022-01-27 11:28 ` [PATCH v2 3/5] modules: Introduce data_layout Christophe Leroy 2022-01-27 11:28 ` Christophe Leroy 2022-01-27 11:28 ` [PATCH v2 4/5] modules: Add CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC Christophe Leroy 2022-01-27 11:28 ` Christophe Leroy 2022-01-28 14:09 ` Daniel Thompson 2022-01-28 14:09 ` Daniel Thompson 2022-01-27 11:28 ` [PATCH v2 5/5] powerpc: Select ARCH_WANTS_MODULES_DATA_IN_VMALLOC on book3s/32 and 8xx Christophe Leroy 2022-01-27 11:28 ` Christophe Leroy 2022-02-02 23:36 ` Luis Chamberlain 2022-02-02 23:36 ` Luis Chamberlain 2022-02-03 5:39 ` Michael Ellerman 2022-02-03 5:39 ` Michael Ellerman 2022-02-03 7:07 ` Christophe Leroy 2022-02-03 7:07 ` Christophe Leroy 2022-02-07 1:19 ` Michael Ellerman 2022-02-07 1:19 ` Michael Ellerman 2022-02-09 15:42 ` [PATCH v2 0/5] Allocate module text and data separately Miroslav Benes 2022-02-09 15:42 ` Miroslav Benes
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=cover.1643282353.git.christophe.leroy@csgroup.eu \ --to=christophe.leroy@csgroup.eu \ --cc=jeyu@kernel.org \ --cc=kgdb-bugreport@lists.sourceforge.net \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mcgrof@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: linkBe 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.