From: Zhou Chengming <zhouchengming1@huawei.com>
To: <mingo@redhat.com>, <tglx@linutronix.de>, <peterz@infradead.org>,
<hpa@zytor.com>, <bp@suse.de>, <jkosina@suse.cz>,
<rostedt@goodmis.org>, <mjurczyk@google.com>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<zhouchengming1@huawei.com>
Subject: [PATCH] x86/alternatives: free smp_alt_modules when enable smp
Date: Fri, 27 Oct 2017 15:18:12 +0800 [thread overview]
Message-ID: <1509088692-9971-1-git-send-email-zhouchengming1@huawei.com> (raw)
In the current code, we don't free smp_alt_modules when enable smp,
so have to wait module unload to call alternatives_smp_module_del()
to free its smp_alt_module. This strategy has shortcomings.
We can make sure smp_alt_modules will be useless after enable smp,
so free it all. And alternatives_smp_module_del() can return directly
when !uniproc_patched to avoid a list traversal.
Signed-off-by: Zhou Chengming <zhouchengming1@huawei.com>
---
arch/x86/kernel/alternative.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
index 3344d33..8549269 100644
--- a/arch/x86/kernel/alternative.c
+++ b/arch/x86/kernel/alternative.c
@@ -534,6 +534,9 @@ void __init_or_module alternatives_smp_module_del(struct module *mod)
struct smp_alt_module *item;
mutex_lock(&smp_alt);
+ if (!uniproc_patched)
+ goto unlock;
+
list_for_each_entry(item, &smp_alt_modules, next) {
if (mod != item->mod)
continue;
@@ -541,12 +544,13 @@ void __init_or_module alternatives_smp_module_del(struct module *mod)
kfree(item);
break;
}
+unlock:
mutex_unlock(&smp_alt);
}
void alternatives_enable_smp(void)
{
- struct smp_alt_module *mod;
+ struct smp_alt_module *mod, *tmp;
/* Why bother if there are no other CPUs? */
BUG_ON(num_possible_cpus() == 1);
@@ -558,9 +562,12 @@ void alternatives_enable_smp(void)
BUG_ON(num_online_cpus() != 1);
clear_cpu_cap(&boot_cpu_data, X86_FEATURE_UP);
clear_cpu_cap(&cpu_data(0), X86_FEATURE_UP);
- list_for_each_entry(mod, &smp_alt_modules, next)
+ list_for_each_entry_safe(mod, tmp, &smp_alt_modules, next) {
alternatives_smp_lock(mod->locks, mod->locks_end,
mod->text, mod->text_end);
+ list_del(&mod->next);
+ kfree(mod);
+ }
uniproc_patched = false;
}
mutex_unlock(&smp_alt);
--
1.8.3.1
next reply other threads:[~2017-10-27 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 7:18 Zhou Chengming [this message]
2017-10-27 7:49 ` Borislav Petkov
2017-10-27 8:11 ` zhouchengming
2017-10-27 8:27 ` Borislav Petkov
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=1509088692-9971-1-git-send-email-zhouchengming1@huawei.com \
--to=zhouchengming1@huawei.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjurczyk@google.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®