From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Petr Pavlu <petr.pavlu@suse.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jason Baron <jbaron@akamai.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ard Biesheuvel <ardb@kernel.org>
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] module: Make .static_call_sites read-only after init
Date: Fri, 3 Jan 2025 15:06:28 +0100 [thread overview]
Message-ID: <97beceb2-dd87-4b7f-a269-b6612e5557a3@csgroup.eu> (raw)
In-Reply-To: <20241223093840.29417-1-petr.pavlu@suse.com>
Hi Petr,
Le 23/12/2024 à 10:37, Petr Pavlu a écrit :
> 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.
>
> 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(-)
>
>
We have a problem at the moment with ro_after_init sections, isn't it
better to fix it before adding new stuff to ro_after_init ?
This series conflicts with my series which aims at fixing up
ro_after_init handling in modules, see
https://patchwork.kernel.org/project/linux-modules/cover/cover.1733427536.git.christophe.leroy@csgroup.eu/
I was expecting my series to land in modules-next, do you or Luis plan
to take it anytime soon ?
Christophe
next prev parent reply other threads:[~2025-01-03 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 9:37 Petr Pavlu
2024-12-23 9:37 ` [PATCH 1/3] module: Constify parameters of module_enforce_rwx_sections() Petr Pavlu
2024-12-23 9:37 ` [PATCH 2/3] module: Add a separate function to mark sections as read-only after init Petr Pavlu
2024-12-23 9:37 ` [PATCH 3/3] module: Make .static_call_sites " Petr Pavlu
2025-01-03 14:06 ` Christophe Leroy [this message]
2025-01-03 16:24 ` [PATCH 0/3] " Petr Pavlu
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=97beceb2-dd87-4b7f-a269-b6612e5557a3@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=ardb@kernel.org \
--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=petr.pavlu@suse.com \
--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®