From: Lucas De Marchi <lucas.demarchi@intel.com>
To: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Petr Pavlu <petr.pavlu@suse.com>
Subject: [PATCH 1/2] module: Override -EEXISTS module return
Date: Mon, 13 Oct 2025 09:26:23 -0700 [thread overview]
Message-ID: <20251013-module-warn-ret-v1-1-ab65b41af01f@intel.com> (raw)
In-Reply-To: <20251013-module-warn-ret-v1-0-ab65b41af01f@intel.com>
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.
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) {
--
2.51.0
next prev parent reply other threads:[~2025-10-13 16:27 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 ` Lucas De Marchi [this message]
2025-10-17 12:04 ` [PATCH 1/2] module: Override -EEXISTS module return Petr Pavlu
2025-11-02 18:23 ` Aaron Tomlin
2025-11-10 15:17 ` Daniel Gomez
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=20251013-module-warn-ret-v1-1-ab65b41af01f@intel.com \
--to=lucas.demarchi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--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).