From: Petr Mladek <pmladek@suse.com>
To: Jiri Kosina <jikos@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Miroslav Benes <mbenes@suse.cz>
Cc: Jason Baron <jbaron@akamai.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Jessica Yu <jeyu@kernel.org>,
Evgenii Shatokhin <eshatokhin@virtuozzo.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Petr Mladek <pmladek@suse.com>
Subject: [PATCH v7 0/7] livepatch: Atomic replace feature
Date: Tue, 6 Feb 2018 11:34:17 +0100 [thread overview]
Message-ID: <20180206103424.10829-1-pmladek@suse.com> (raw)
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.
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 (2):
livepatch: Free only structures with initialized kobject
livepatch: Atomic replace and cumulative patches documentation
Documentation/livepatch/cumulative-patches.txt | 76 +++++
include/linux/livepatch.h | 59 +++-
kernel/livepatch/core.c | 378 ++++++++++++++++++++++---
kernel/livepatch/core.h | 4 +
kernel/livepatch/patch.c | 29 +-
kernel/livepatch/patch.h | 4 +-
kernel/livepatch/transition.c | 41 ++-
7 files changed, 543 insertions(+), 48 deletions(-)
create mode 100644 Documentation/livepatch/cumulative-patches.txt
--
2.13.6
next reply other threads:[~2018-02-06 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 10:34 Petr Mladek [this message]
2018-02-06 10:34 ` [PATCH v7 1/7] livepatch: Use lists to manage patches, objects and functions Petr Mladek
2018-02-09 10:06 ` Miroslav Benes
2018-02-06 10:34 ` [PATCH v7 2/7] livepatch: Free only structures with initialized kobject Petr Mladek
2018-02-09 10:06 ` Miroslav Benes
2018-02-06 10:34 ` [PATCH v7 3/7] livepatch: Initial support for dynamic structures Petr Mladek
2018-02-09 10:06 ` Miroslav Benes
2018-02-06 10:34 ` [PATCH v7 4/7] livepatch: Allow to unpatch only functions of the given type Petr Mladek
2018-02-09 12:29 ` Miroslav Benes
2018-02-06 10:34 ` [PATCH v7 5/7] livepatch: Support separate list for replaced patches Petr Mladek
2018-02-09 12:59 ` Miroslav Benes
2018-02-06 10:34 ` [PATCH v7 6/7] livepatch: Add atomic replace Petr Mladek
2018-02-12 15:54 ` Miroslav Benes
2018-02-06 10:34 ` [PATCH v7 7/7] livepatch: Atomic replace and cumulative patches documentation Petr Mladek
2018-02-06 17:07 ` Joe Lawrence
2018-02-14 16:16 ` [PATCH v7 0/7] livepatch: Atomic replace feature Miroslav Benes
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=20180206103424.10829-1-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=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 \
/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®