[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <851c227e-5d1e-44bb-80ca-d9e230e8ccfe@kernel.org>
Date: Mon, 1 Sep 2025 20:29:00 +0200
From: Daniel Gomez <da.gomez@...nel.org>
To: Jinchao Wang <wangjinchao600@...il.com>,
Luis Chamberlain <mcgrof@...nel.org>, Petr Pavlu <petr.pavlu@...e.com>,
Sami Tolvanen <samitolvanen@...gle.com>, linux-modules@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/4] module: show why force load fails
On 29/08/2025 10.49, Jinchao Wang wrote:
> Include reason in error message when force loading is disabled.
>
> Signed-off-by: Jinchao Wang <wangjinchao600@...il.com>
> ---
> kernel/module/main.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/module/main.c b/kernel/module/main.c
> index c66b26184936..e7484c6ce6e3 100644
> --- a/kernel/module/main.c
> +++ b/kernel/module/main.c
> @@ -1083,6 +1083,7 @@ int try_to_force_load(struct module *mod, const char *reason)
> add_taint_module(mod, TAINT_FORCED_MODULE, LOCKDEP_NOW_UNRELIABLE);
> return 0;
> #else
> + pr_err("%s: %s, force load is not supported\n", mod->name, reason);
> return -ENOEXEC;
> #endif
> }
I don't think is good to inform via kernel log buffer what the kernel supports
or what not. And definitely, not as an error.
Powered by blists - more mailing lists