[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250306131430.7016-1-petr.pavlu@suse.com>
Date: Thu, 6 Mar 2025 14:13:51 +0100
From: Petr Pavlu <petr.pavlu@...e.com>
To: Luis Chamberlain <mcgrof@...nel.org>,
Petr Pavlu <petr.pavlu@...e.com>,
Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Jason Baron <jbaron@...mai.com>
Cc: Sami Tolvanen <samitolvanen@...gle.com>,
Daniel Gomez <da.gomez@...sung.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ard Biesheuvel <ardb@...nel.org>,
Christophe Leroy <christophe.leroy@...roup.eu>,
linux-modules@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/3] module: Make .static_call_sites read-only after init
Section .static_call_sites holds data structures that need to be sorted and
processed only at module load time. The section is never modified
afterwards. Make it therefore read-only after module initialization to
avoid any (non-)accidental modifications.
Changes since v1 [1]:
* Rebase the patches. The kernel now has commit 110b1e070f1d ("module:
Don't fail module loading when setting ro_after_init section RO failed")
which addresses a previous problem with handling ro_after_init sections.
[1] https://lore.kernel.org/linux-modules/20241223093840.29417-1-petr.pavlu@suse.com/
Petr Pavlu (3):
module: Constify parameters of module_enforce_rwx_sections()
module: Add a separate function to mark sections as read-only after
init
module: Make .static_call_sites read-only after init
kernel/module/internal.h | 7 ++++--
kernel/module/main.c | 18 +++------------
kernel/module/strict_rwx.c | 47 ++++++++++++++++++++++++++++++++++++--
3 files changed, 53 insertions(+), 19 deletions(-)
base-commit: 848e076317446f9c663771ddec142d7c2eb4cb43
--
2.43.0
Powered by blists - more mailing lists