From: Petr Pavlu <petr.pavlu@suse.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>
Cc: Aaron Tomlin <atomlin@atomlin.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 4/6] module/dups: Use scope-based cleanup helpers
Date: Thu, 23 Jul 2026 10:25:54 +0200 [thread overview]
Message-ID: <20260723-module-stats-rcu-v2-4-bd582261fae3@suse.com> (raw)
In-Reply-To: <20260723-module-stats-rcu-v2-0-bd582261fae3@suse.com>
Use scope-based cleanup helpers for kmod_dup_mutex and kmod_req to shorten
the code and to clarify where the lock is taken in
kmod_dup_request_exists_wait().
Signed-off-by: Petr Pavlu <petr.pavlu@suse.com>
---
kernel/module/dups.c | 56 +++++++++++++++++++++-------------------------------
1 file changed, 23 insertions(+), 33 deletions(-)
diff --git a/kernel/module/dups.c b/kernel/module/dups.c
index 0f6bb05b2d81..56d659f049c5 100644
--- a/kernel/module/dups.c
+++ b/kernel/module/dups.c
@@ -63,6 +63,8 @@ static void put_kmod_req(struct kmod_dup_req *kmod_req)
kfree(kmod_req);
}
+DEFINE_FREE(put_kmod_req, struct kmod_dup_req *, if (_T) put_kmod_req(_T))
+
static struct kmod_dup_req *kmod_dup_request_lookup(char *module_name)
{
struct kmod_dup_req *kmod_req;
@@ -97,9 +99,8 @@ static void kmod_dup_request_delete(struct work_struct *work)
* kmod. The inneficies there are a call to modprobe and modprobe
* just returning 0.
*/
- mutex_lock(&kmod_dup_mutex);
- list_del(&kmod_req->list);
- mutex_unlock(&kmod_dup_mutex);
+ scoped_guard(mutex, &kmod_dup_mutex)
+ list_del(&kmod_req->list);
put_kmod_req(kmod_req);
}
@@ -120,15 +121,18 @@ static struct kmod_dup_req *alloc_kmod_req(const char *module_name)
bool kmod_dup_request_exists_wait(char *module_name, bool wait, int *dup_ret)
{
- struct kmod_dup_req *kmod_req;
+ struct kmod_dup_req *kmod_req __free(put_kmod_req) = NULL;
int ret;
- mutex_lock(&kmod_dup_mutex);
-
- kmod_req = kmod_dup_request_lookup(module_name);
- if (!kmod_req) {
+ scoped_guard(mutex, &kmod_dup_mutex) {
struct kmod_dup_req *new_kmod_req;
+ kmod_req = kmod_dup_request_lookup(module_name);
+ if (kmod_req) {
+ get_kmod_req(kmod_req);
+ break;
+ }
+
/*
* If the first request that came through for a module
* was with request_module_nowait() we cannot wait for it
@@ -142,7 +146,6 @@ bool kmod_dup_request_exists_wait(char *module_name, bool wait, int *dup_ret)
*/
if (!wait) {
pr_debug("New request_module_nowait() for %s -- cannot track duplicates for this request\n", module_name);
- mutex_unlock(&kmod_dup_mutex);
return false;
}
@@ -152,18 +155,12 @@ bool kmod_dup_request_exists_wait(char *module_name, bool wait, int *dup_ret)
*/
pr_debug("New request_module() for %s\n", module_name);
new_kmod_req = alloc_kmod_req(module_name);
- if (!new_kmod_req) {
- mutex_unlock(&kmod_dup_mutex);
+ if (!new_kmod_req)
return false;
- }
list_add(&new_kmod_req->list, &dup_kmod_reqs);
- mutex_unlock(&kmod_dup_mutex);
return false;
}
- get_kmod_req(kmod_req);
- mutex_unlock(&kmod_dup_mutex);
-
/* We are dealing with a duplicate request now */
/*
@@ -190,7 +187,7 @@ bool kmod_dup_request_exists_wait(char *module_name, bool wait, int *dup_ret)
* calls bail out right away.
*/
*dup_ret = 0;
- goto out;
+ return true;
}
/*
@@ -205,14 +202,11 @@ bool kmod_dup_request_exists_wait(char *module_name, bool wait, int *dup_ret)
TASK_KILLABLE);
if (ret) {
*dup_ret = ret;
- goto out;
+ return true;
}
/* Now the duplicate request has the same exact return value as the first request */
*dup_ret = kmod_req->dup_ret;
-
-out:
- put_kmod_req(kmod_req);
return true;
}
@@ -220,26 +214,22 @@ void kmod_dup_request_announce(char *module_name, int ret)
{
struct kmod_dup_req *kmod_req;
- mutex_lock(&kmod_dup_mutex);
-
/*
* Look for a kmod_dup_req previously added in
* kmod_dup_request_exists_wait(). Note that a request_module_nowait()
* without its own kmod_dup_req entry can announce a result of
* a concurrent request_module() call.
*/
- kmod_req = kmod_dup_request_lookup(module_name);
- if (!kmod_req || completion_done(&kmod_req->first_req_done)) {
- mutex_unlock(&kmod_dup_mutex);
- return;
- }
-
- kmod_req->dup_ret = ret;
+ scoped_guard(mutex, &kmod_dup_mutex) {
+ kmod_req = kmod_dup_request_lookup(module_name);
+ if (!kmod_req || completion_done(&kmod_req->first_req_done))
+ return;
- /* Inform all duplicate waiters to check the return value. */
- complete_all(&kmod_req->first_req_done);
+ kmod_req->dup_ret = ret;
- mutex_unlock(&kmod_dup_mutex);
+ /* Inform all duplicate waiters to check the return value. */
+ complete_all(&kmod_req->first_req_done);
+ }
/*
* Now that we have allowed prior request_module() calls to go on
--
2.54.0
next prev parent reply other threads:[~2026-07-23 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 8:25 [PATCH v2 0/6] module/dups: Fix a use-after-free and improve the code Petr Pavlu
2026-07-23 8:25 ` [PATCH v2 1/6] module/dups: Inform duplicate requests about the result directly Petr Pavlu
2026-07-23 8:41 ` sashiko-bot
2026-07-23 8:25 ` [PATCH v2 2/6] module/dups: Fix use-after-free in kmod_dup_req lifetime handling Petr Pavlu
2026-07-24 2:50 ` Aaron Tomlin
2026-07-23 8:25 ` [PATCH v2 3/6] module/dups: Avoid unnecessary kmod_dup_req allocations Petr Pavlu
2026-07-24 2:53 ` Aaron Tomlin
2026-07-23 8:25 ` Petr Pavlu [this message]
2026-07-23 8:25 ` [PATCH v2 5/6] module/dups: Use strcmp() to compare module names Petr Pavlu
2026-07-23 8:25 ` [PATCH v2 6/6] module/dups: Clean up includes 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=20260723-module-stats-rcu-v2-4-bd582261fae3@suse.com \
--to=petr.pavlu@suse.com \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.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