From: Evgenii Shatokhin <eshatokhin@virtuozzo.com>
To: Petr Mladek <pmladek@suse.com>, Jason Baron <jbaron@akamai.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Miroslav Benes <mbenes@suse.cz>,
Joe Lawrence <joe.lawrence@redhat.com>,
Jessica Yu <jeyu@kernel.org>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/8] livepatch: Atomic replace feature
Date: Mon, 5 Mar 2018 13:56:40 +0300 [thread overview]
Message-ID: <5c956014-b717-aed8-de1b-58967ef835c6@virtuozzo.com> (raw)
In-Reply-To: <20180221132914.4809-1-pmladek@suse.com>
Hi,
Petr, Jason - thanks a lot for working on this series, first of all! And
especially for your patience.
On 21.02.2018 16:29, Petr Mladek wrote:
> The atomic replace allows to create cumulative patches. They
> are useful when you maintain many livepatches and want to remove
> one that is lower on the stack. In addition it is very useful when
> more patches touch the same function and there are dependencies
> between them.
I have experimented with this updated patchset a bit.
It looks like replace operation fails if there is a loaded but disabled
patch.
Suppose there are 2 binary patches changing the same kernel functions.
Load patch1, then disable it (echo 0 >
/sys/kernel/livepatch/patch1/enabled), then try load patch2 with atomic
replace. I get "Device or resource busy" error at this point.
It seems, __klp_enable_patch() returns -EBUSY for some reason. I haven't
dug deeper into that code yet.
A workaround is simple: just unload all disabled patches before trying
to load patch2 with replace. Still, the behavior is quite strange.
>
> I have found one bug in v7. We were not able to initialize NOP
> struct klp_func when the patches module is not loaded. It was
> because func->new_func was NULL. I have fixed it in separate patch
> for an easier review.
>
> Note that the original Jason's patch did not have this problem
> because func->new_func was always NULL there. But this required
> NOP-specific handling also on other locations, namely
> klp_ftrace_handler() and klp_check_stack_func().
>
> Changes against v7:
>
> + Fixed handling of NOPs for not-yet-loaded modules
> + Made klp_replaced_patches list static [Mirek]
> + Made klp_free_object() public later [Mirek]
> + Fixed several reported typos [Mirek, Joe]
> + Updated documentation according to the feedback [Joe]
> + Added some Acks [Mirek]
>
> Changes against v6:
>
> + used list_move when disabling replaced patches [Jason]
> + renamed KLP_FUNC_ORIGINAL -> KLP_FUNC_STATIC [Mirek]
> + used klp_is_func_type() in klp_unpatch_object() [Mirek]
> + moved static definition of klp_get_or_add_object() [Mirek]
> + updated comment about synchronization in forced mode [Mirek]
> + added user documentation
> + fixed several typos
>
> Jason Baron (5):
> livepatch: Use lists to manage patches, objects and functions
> livepatch: Initial support for dynamic structures
> livepatch: Allow to unpatch only functions of the given type
> livepatch: Support separate list for replaced patches.
> livepatch: Add atomic replace
>
> Petr Mladek (3):
> livepatch: Free only structures with initialized kobject
> livepatch: Correctly handle atomic replace for not yet loaded modules
> livepatch: Atomic replace and cumulative patches documentation
>
> Documentation/livepatch/cumulative-patches.txt | 83 ++++++
> include/linux/livepatch.h | 59 +++-
> kernel/livepatch/core.c | 394 ++++++++++++++++++++++---
> kernel/livepatch/core.h | 4 +
> kernel/livepatch/patch.c | 31 +-
> kernel/livepatch/patch.h | 4 +-
> kernel/livepatch/transition.c | 41 ++-
> 7 files changed, 566 insertions(+), 50 deletions(-)
> create mode 100644 Documentation/livepatch/cumulative-patches.txt
>
Regards,
Evgenii
next prev parent reply other threads:[~2018-03-05 10:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 13:29 Petr Mladek
2018-02-21 13:29 ` [PATCH v8 1/8] livepatch: Use lists to manage patches, objects and functions Petr Mladek
2018-02-21 13:29 ` [PATCH v8 2/8] livepatch: Free only structures with initialized kobject Petr Mladek
2018-02-21 13:29 ` [PATCH v8 3/8] livepatch: Initial support for dynamic structures Petr Mladek
2018-02-21 13:29 ` [PATCH v8 4/8] livepatch: Allow to unpatch only functions of the given type Petr Mladek
2018-02-22 15:25 ` Miroslav Benes
2018-02-21 13:29 ` [PATCH v8 5/8] livepatch: Support separate list for replaced patches Petr Mladek
2018-02-21 13:29 ` [PATCH v8 6/8] livepatch: Add atomic replace Petr Mladek
2018-02-21 13:29 ` [PATCH v8 7/8] livepatch: Correctly handle atomic replace for not yet loaded modules Petr Mladek
2018-02-22 21:00 ` Miroslav Benes
2018-03-01 10:28 ` Petr Mladek
2018-03-02 22:00 ` Joe Lawrence
2018-03-05 9:54 ` Miroslav Benes
2018-03-05 14:42 ` Josh Poimboeuf
2018-03-06 14:10 ` Petr Mladek
2018-02-21 13:29 ` [PATCH v8 8/8] livepatch: Atomic replace and cumulative patches documentation Petr Mladek
2018-02-23 10:41 ` Miroslav Benes
2018-02-23 16:55 ` Joe Lawrence
2018-02-23 20:40 ` Miroslav Benes
2018-02-22 15:23 ` [PATCH v8 0/8] livepatch: Atomic replace feature Miroslav Benes
2018-03-05 10:56 ` Evgenii Shatokhin [this message]
2018-03-05 12:54 ` Miroslav Benes
2018-03-06 15:32 ` Petr Mladek
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=5c956014-b717-aed8-de1b-58967ef835c6@virtuozzo.com \
--to=eshatokhin@virtuozzo.com \
--cc=jbaron@akamai.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--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
all inboxes | Powered by JetHome®