From: Petr Pavlu <petr.pavlu@suse.com>
To: Petr Pavlu <petr.pavlu@suse.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jason Baron <jbaron@akamai.com>
Cc: Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ard Biesheuvel <ardb@kernel.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] module: Make .static_call_sites read-only after init
Date: Mon, 7 Apr 2025 16:14:34 +0200 [thread overview]
Message-ID: <fc5a960f-21d4-4110-88db-20c103491af6@suse.com> (raw)
In-Reply-To: <20250306131430.7016-1-petr.pavlu@suse.com>
On 3/6/25 14:13, Petr Pavlu wrote:
> 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(-)
Queued now on modules-next, for 6.16-rc1.
-- Petr
prev parent reply other threads:[~2025-04-07 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 13:13 Petr Pavlu
2025-03-06 13:13 ` [PATCH v2 1/3] module: Constify parameters of module_enforce_rwx_sections() Petr Pavlu
2025-03-06 13:13 ` [PATCH v2 2/3] module: Add a separate function to mark sections as read-only after init Petr Pavlu
2025-03-06 13:13 ` [PATCH v2 3/3] module: Make .static_call_sites " Petr Pavlu
2025-03-06 17:28 ` Christophe Leroy
2025-03-07 0:12 ` Sami Tolvanen
2025-03-12 12:05 ` Petr Pavlu
2025-03-12 23:21 ` Sami Tolvanen
2025-03-13 8:17 ` Petr Pavlu
2025-03-06 17:16 ` [PATCH v2 0/3] " Luis Chamberlain
2025-04-07 14:14 ` Petr Pavlu [this message]
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=fc5a960f-21d4-4110-88db-20c103491af6@suse.com \
--to=petr.pavlu@suse.com \
--cc=ardb@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=da.gomez@samsung.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
/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
all inboxes | Powered by JetHome®