linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@samsung.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Kees Cook <kees@kernel.org>, <linux-modules@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC PATCH 3/3] module: pre-test setting ro_after_init data read-only
Date: Sat, 9 Nov 2024 22:03:06 +0100	[thread overview]
Message-ID: <D5HYAAW77P1A.6KLS8F6CVKGS@samsung.com> (raw)
In-Reply-To: <a32f2390caf6e0d157ffea6e04f5e5d8629620c2.1731148254.git.christophe.leroy@csgroup.eu>

On Sat Nov 9, 2024 at 11:35 AM CET, Christophe Leroy wrote:
> To be on the safe side, try to set ro_after_init data section readonly
> at the same time as rodata. If it fails it will likely fail again
> later so let's cancel module loading while we still can do it.
> If it doesn't fail, put it back to read-only, continue module loading

I think you mean put it back to rw?

> and cross fingers so that it still works after module init. Then it
> should in principle never fail so add a WARN_ON_ONCE() to get a big
> fat warning in case it happens anyway.

I agree this is the best we can do. But I don't think there's any
guarantee that we won't fail on the second try?

>
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
>  kernel/module/main.c       | 2 +-
>  kernel/module/strict_rwx.c | 5 ++++-
>  2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/module/main.c b/kernel/module/main.c
> index 1bf4b0db291b..b603c9647e73 100644
> --- a/kernel/module/main.c
> +++ b/kernel/module/main.c
> @@ -2582,7 +2582,7 @@ static noinline int do_init_module(struct module *mod)
>  	rcu_assign_pointer(mod->kallsyms, &mod->core_kallsyms);
>  #endif
>  	ret = module_enable_rodata_ro_after_init(mod);
> -	if (ret)
> +	if (WARN_ON_ONCE(ret))
>  		pr_warn("%s: %s() returned %d, ro_after_init data might still be writable\n",
>  			mod->name, __func__, ret);
>  
> diff --git a/kernel/module/strict_rwx.c b/kernel/module/strict_rwx.c
> index f68c59974ae2..329afd43f06b 100644
> --- a/kernel/module/strict_rwx.c
> +++ b/kernel/module/strict_rwx.c
> @@ -58,7 +58,10 @@ int module_enable_rodata_ro(const struct module *mod)
>  	if (ret)
>  		return ret;
>  
> -	return 0;
> +	ret = module_set_memory(mod, MOD_RO_AFTER_INIT, set_memory_ro);
> +	if (ret)
> +		return ret;
> +	return module_set_memory(mod, MOD_RO_AFTER_INIT, set_memory_rw);
>  }
>  
>  int module_enable_rodata_ro_after_init(const struct module *mod)


  reply	other threads:[~2024-11-09 21:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20241109103551eucas1p1bddb2f2d9a898aba967868dece7cd685@eucas1p1.samsung.com>
2024-11-09 10:35 ` [RFC PATCH 1/3] module: Split module_enable_rodata_ro() Christophe Leroy
2024-11-09 10:35   ` [RFC PATCH 2/3] module: Don't fail module loading when setting ro_after_init section RO failed Christophe Leroy
2024-11-09 22:17     ` Daniel Gomez
2024-11-11 18:53       ` Christophe Leroy
2024-11-12  9:43         ` Daniel Gomez
2024-11-12 11:08           ` Christophe Leroy
2024-11-12 14:35           ` Petr Pavlu
2024-11-28 20:23             ` Daniel Gomez
2024-12-04 15:14               ` Petr Pavlu
2024-12-10 10:49                 ` Daniel Gomez
2024-12-11  8:46                   ` Daniel Gomez
2025-01-03 15:40                   ` Petr Pavlu
2025-01-04  7:42                     ` Christophe Leroy
2024-11-11 17:05     ` Petr Pavlu
2024-11-09 10:35   ` [RFC PATCH 3/3] module: pre-test setting ro_after_init data read-only Christophe Leroy
2024-11-09 21:03     ` Daniel Gomez [this message]
2024-11-11 18:55       ` Christophe Leroy
2024-11-12 20:28     ` Luis Chamberlain
2024-11-13  6:49       ` Christophe Leroy
2024-11-13  9:56         ` Luis Chamberlain
2024-11-09 22:18   ` [RFC PATCH 1/3] module: Split module_enable_rodata_ro() Daniel Gomez
2024-11-26 19:58   ` Luis Chamberlain
2024-11-27 13:37     ` Christophe Leroy
2024-11-27 18:55       ` 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=D5HYAAW77P1A.6KLS8F6CVKGS@samsung.com \
    --to=da.gomez@samsung.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=samitolvanen@google.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).