From: Daniel Gomez <da.gomez@kernel.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Petr Pavlu <petr.pavlu@suse.com>
Subject: Re: [PATCH 1/2] module: Override -EEXISTS module return
Date: Mon, 10 Nov 2025 16:17:47 +0100 [thread overview]
Message-ID: <ea36d12b-15b9-4c1c-b81f-75834bc3269a@kernel.org> (raw)
In-Reply-To: <20251013-module-warn-ret-v1-1-ab65b41af01f@intel.com>
On 13/10/2025 18.26, Lucas De Marchi wrote:
> The -EEXIST errno is reserved by the module loading functionality. When
> userspace calls [f]init_module(), it expects a -EEXIST to mean that the
> module is already loaded in the kernel. If module_init() returns it,
> that is not true anymore.
>
> Add a warning and override the return code to workaround modules
> currently returning the wrong code. It's expected that they eventually
> migrate to a better suited error.
I've been following the thread (and apologies for the delay) and reviewing the
patches, and I do not believe we should push this workaround. While this "fixes"
the bug reported, it also hides the real problem and drivers will continue
misusing EEXIST at module initialization.
From the bug report thread, I agree with Christophe's suggestion that
nf_conntrack_helpers_register() should return EBUSY instead of EEXIST. This
would fix the root cause for this particular module and will allow others to
change their module behavior, if we also follow up with proper documentation
about EEXIST.
>
> Closes: https://lore.kernel.org/all/aKLzsAX14ybEjHfJ@orbyte.nwl.cc/
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> kernel/module/main.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/kernel/module/main.c b/kernel/module/main.c
> index c66b261849362..74ff87b13c517 100644
> --- a/kernel/module/main.c
> +++ b/kernel/module/main.c
> @@ -3038,6 +3038,11 @@ static noinline int do_init_module(struct module *mod)
> if (mod->init != NULL)
> ret = do_one_initcall(mod->init);
> if (ret < 0) {
> + if (ret == -EEXIST) {
> + pr_warn("%s: init suspiciously returned -EEXIST: Overriding with -EBUSY\n",
> + mod->name);
> + ret = -EBUSY;
> + }
> goto fail_free_freeinit;
> }
> if (ret > 0) {
>
next prev parent reply other threads:[~2025-11-10 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 16:26 [PATCH 0/2] module: Tweak return and warning Lucas De Marchi
2025-10-13 16:26 ` [PATCH 1/2] module: Override -EEXISTS module return Lucas De Marchi
2025-10-17 12:04 ` Petr Pavlu
2025-11-02 18:23 ` Aaron Tomlin
2025-11-10 15:17 ` Daniel Gomez [this message]
2025-11-10 15:31 ` Lucas De Marchi
2025-11-16 20:42 ` Daniel Gomez
2025-11-16 20:46 ` Daniel Gomez
2025-10-13 16:26 ` [PATCH 2/2] module: Simplify warning on positive returns from module_init() Lucas De Marchi
2025-10-17 12:06 ` Petr Pavlu
2025-11-02 18:23 ` Aaron Tomlin
2025-11-16 20:47 ` [PATCH 0/2] module: Tweak return and warning Daniel Gomez
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=ea36d12b-15b9-4c1c-b81f-75834bc3269a@kernel.org \
--to=da.gomez@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=petr.pavlu@suse.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;
as well as URLs for NNTP newsgroup(s).