From: Yafang Shao <laoar.shao@gmail.com>
To: jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
pmladek@suse.com, joe.lawrence@redhat.com, mcgrof@kernel.org
Cc: live-patching@vger.kernel.org, linux-modules@vger.kernel.org,
Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH] livepatch: Delete the associated module when replacing an old livepatch
Date: Sun, 31 Mar 2024 21:38:39 +0800 [thread overview]
Message-ID: <20240331133839.18316-1-laoar.shao@gmail.com> (raw)
Enhance the functionality of kpatch to automatically remove the associated
module when replacing an old livepatch with a new one. This ensures that no
leftover modules remain in the system. For instance:
- Load the first livepatch
$ kpatch load 6.9.0-rc1+/livepatch-test_0.ko
loading patch module: 6.9.0-rc1+/livepatch-test_0.ko
waiting (up to 15 seconds) for patch transition to complete...
transition complete (2 seconds)
$ kpatch list
Loaded patch modules:
livepatch_test_0 [enabled]
$ lsmod |grep livepatch
livepatch_test_0 16384 1
- Load a new livepatch
$ kpatch load 6.9.0-rc1+/livepatch-test_1.ko
loading patch module: 6.9.0-rc1+/livepatch-test_1.ko
waiting (up to 15 seconds) for patch transition to complete...
transition complete (2 seconds)
$ kpatch list
Loaded patch modules:
livepatch_test_1 [enabled]
$ lsmod |grep livepatch
livepatch_test_1 16384 1
livepatch_test_0 16384 0 <<<< leftover
With this improvement, executing
`kpatch load 6.9.0-rc1+/livepatch-test_1.ko` will automatically remove the
livepatch-test_0.ko module.
Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
---
include/linux/module.h | 1 +
kernel/livepatch/core.c | 11 +++++++++--
kernel/module/main.c | 43 ++++++++++++++++++++++++-----------------
3 files changed, 35 insertions(+), 20 deletions(-)
diff --git a/include/linux/module.h b/include/linux/module.h
index 1153b0d99a80..9a95174a919b 100644
--- a/include/linux/module.h
+++ b/include/linux/module.h
@@ -75,6 +75,7 @@ extern struct module_attribute module_uevent;
/* These are either module local, or the kernel's dummy ones. */
extern int init_module(void);
extern void cleanup_module(void);
+extern void delete_module(struct module *mod);
#ifndef MODULE
/**
diff --git a/kernel/livepatch/core.c b/kernel/livepatch/core.c
index ecbc9b6aba3a..f1edc999f3ef 100644
--- a/kernel/livepatch/core.c
+++ b/kernel/livepatch/core.c
@@ -711,6 +711,8 @@ static void klp_free_patch_start(struct klp_patch *patch)
*/
static void klp_free_patch_finish(struct klp_patch *patch)
{
+ struct module *mod = patch->mod;
+
/*
* Avoid deadlock with enabled_store() sysfs callback by
* calling this outside klp_mutex. It is safe because
@@ -721,8 +723,13 @@ static void klp_free_patch_finish(struct klp_patch *patch)
wait_for_completion(&patch->finish);
/* Put the module after the last access to struct klp_patch. */
- if (!patch->forced)
- module_put(patch->mod);
+ if (!patch->forced) {
+ module_put(mod);
+ if (module_refcount(mod))
+ return;
+ mod->state = MODULE_STATE_GOING;
+ delete_module(mod);
+ }
}
/*
diff --git a/kernel/module/main.c b/kernel/module/main.c
index e1e8a7a9d6c1..e863e1f87dfd 100644
--- a/kernel/module/main.c
+++ b/kernel/module/main.c
@@ -695,12 +695,35 @@ EXPORT_SYMBOL(module_refcount);
/* This exists whether we can unload or not */
static void free_module(struct module *mod);
+void delete_module(struct module *mod)
+{
+ char buf[MODULE_FLAGS_BUF_SIZE];
+
+ /* Final destruction now no one is using it. */
+ if (mod->exit != NULL)
+ mod->exit();
+ blocking_notifier_call_chain(&module_notify_list,
+ MODULE_STATE_GOING, mod);
+ klp_module_going(mod);
+ ftrace_release_mod(mod);
+
+ async_synchronize_full();
+
+ /* Store the name and taints of the last unloaded module for diagnostic purposes */
+ strscpy(last_unloaded_module.name, mod->name, sizeof(last_unloaded_module.name));
+ strscpy(last_unloaded_module.taints, module_flags(mod, buf, false),
+ sizeof(last_unloaded_module.taints));
+
+ free_module(mod);
+ /* someone could wait for the module in add_unformed_module() */
+ wake_up_all(&module_wq);
+}
+
SYSCALL_DEFINE2(delete_module, const char __user *, name_user,
unsigned int, flags)
{
struct module *mod;
char name[MODULE_NAME_LEN];
- char buf[MODULE_FLAGS_BUF_SIZE];
int ret, forced = 0;
if (!capable(CAP_SYS_MODULE) || modules_disabled)
@@ -750,23 +773,7 @@ SYSCALL_DEFINE2(delete_module, const char __user *, name_user,
goto out;
mutex_unlock(&module_mutex);
- /* Final destruction now no one is using it. */
- if (mod->exit != NULL)
- mod->exit();
- blocking_notifier_call_chain(&module_notify_list,
- MODULE_STATE_GOING, mod);
- klp_module_going(mod);
- ftrace_release_mod(mod);
-
- async_synchronize_full();
-
- /* Store the name and taints of the last unloaded module for diagnostic purposes */
- strscpy(last_unloaded_module.name, mod->name, sizeof(last_unloaded_module.name));
- strscpy(last_unloaded_module.taints, module_flags(mod, buf, false), sizeof(last_unloaded_module.taints));
-
- free_module(mod);
- /* someone could wait for the module in add_unformed_module() */
- wake_up_all(&module_wq);
+ delete_module(mod);
return 0;
out:
mutex_unlock(&module_mutex);
--
2.39.1
next reply other threads:[~2024-03-31 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 13:38 Yafang Shao [this message]
2024-04-01 14:51 ` [PATCH] livepatch: Delete the associated module when replacing an old livepatch zhang warden
2024-04-02 2:27 ` Yafang Shao
2024-04-02 2:56 ` zhang warden
2024-04-02 4:29 ` Yafang Shao
2024-04-01 15:02 ` Joe Lawrence
2024-04-02 2:45 ` Yafang Shao
2024-04-02 13:39 ` Joe Lawrence
2024-04-03 3:19 ` Yafang Shao
2024-04-05 11:46 ` Miroslav Benes
2024-04-04 14:04 ` Petr Mladek
2024-04-06 13:02 ` Yafang Shao
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=20240331133839.18316-1-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=pmladek@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 read-only IMAP folder(s) and NNTP newsgroup(s).