From: Petr Mladek <pmladek@suse.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>, Miroslav Benes <mbenes@suse.cz>
Cc: Jessica Yu <jeyu@redhat.com>, Jiri Kosina <jikos@kernel.org>,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
Petr Mladek <pmladek@suse.com>
Subject: [PATCH] livepatch: Cancel transition a safe way for immediate patches
Date: Tue, 11 Apr 2017 13:07:48 +0200 [thread overview]
Message-ID: <1491908868-27766-1-git-send-email-pmladek@suse.com> (raw)
klp_init_transition() does not set func->transition for immediate patches.
Then klp_ftrace_handler() could use the new code immediately. As a result,
it is not safe to put the livepatch module in klp_cancel_transition().
This patch reverts most of the last minute changes klp_cancel_transition().
It keeps the warning about a misuse because it still makes sense.
Signed-off-by: Petr Mladek <pmladek@suse.com>
---
Hi,
I am afraid that Mirek was not right in the mail
https://lkml.kernel.org/r/alpine.LSU.2.20.1702161504020.16310@pobox.suse.cz
IMHO, it is not safe to put the module when the immediate
patch cannot be applied.
Best Regards,
Petr
kernel/livepatch/transition.c | 20 --------------------
1 file changed, 20 deletions(-)
diff --git a/kernel/livepatch/transition.c b/kernel/livepatch/transition.c
index 2de09e0c4e5c..adc0cc64aa4b 100644
--- a/kernel/livepatch/transition.c
+++ b/kernel/livepatch/transition.c
@@ -120,31 +120,11 @@ static void klp_complete_transition(void)
*/
void klp_cancel_transition(void)
{
- struct klp_patch *patch = klp_transition_patch;
- struct klp_object *obj;
- struct klp_func *func;
- bool immediate_func = false;
-
if (WARN_ON_ONCE(klp_target_state != KLP_PATCHED))
return;
klp_target_state = KLP_UNPATCHED;
klp_complete_transition();
-
- /*
- * In the enable error path, even immediate patches can be safely
- * removed because the transition hasn't been started yet.
- *
- * klp_complete_transition() doesn't have a module_put() for immediate
- * patches, so do it here.
- */
- klp_for_each_object(patch, obj)
- klp_for_each_func(obj, func)
- if (func->immediate)
- immediate_func = true;
-
- if (patch->immediate || immediate_func)
- module_put(patch->mod);
}
/*
--
1.8.5.6
next reply other threads:[~2017-04-11 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 11:07 Petr Mladek [this message]
2017-04-11 11:31 ` Miroslav Benes
2017-04-11 15:10 ` Josh Poimboeuf
2017-04-11 18:55 ` Jiri Kosina
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=1491908868-27766-1-git-send-email-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
/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®