From: Miroslav Benes <mbenes@suse.cz>
To: Petr Mladek <pmladek@suse.com>
Cc: jpoimboe@redhat.com, jikos@kernel.org,
Jason Baron <jbaron@akamai.com>,
jeyu@kernel.org, Evgenii Shatokhin <eshatokhin@virtuozzo.com>,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org
Subject: Re: PATCH v6 3/6] livepatch: Initial support for dynamic structures
Date: Wed, 31 Jan 2018 16:39:04 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.1801311637140.7649@pobox.suse.cz> (raw)
In-Reply-To: <20180125160203.28959-4-pmladek@suse.com>
On Thu, 25 Jan 2018, Petr Mladek wrote:
> From: Jason Baron <jbaron@akamai.com>
>
> We are going to add a feature called atomic replace. It will allow to
> create a patch that would replace all already registered patches.
> For this, we will need to dynamically create funcs' and objects'
> for functions that are not longer patched.
>
> This patch adds basic framework to handle such dynamic structures.
>
> It adds enum klp_func_type that allows to distinguish the dynamically
> allocated funcs' structures. Note that objects' structures do not have
> a clear type. Namely the static objects' structures might list both static
> and dynamic funcs' structures.
>
> The function type is then used to limit klp_free() functions. We will
> want to free the dynamic structures separately when they are not
> longer needed. At the same time, we also want to make our life easier,
> and introduce _any_ type that will allow to process all existing
> structures in one go.
>
> We need to be careful here. First, objects' structures must be freed
> only when all listed funcs' structures are freed. Also we must avoid
> double free. Both problems are solved by removing the freed structures
> from the list.
>
> Also note that klp_free*() functions are called also in klp_init_patch()
> error path when only some kobjects have been initialized. The other
> dynamic structures must be freed immediately by calling the respective
> klp_free_*_dynamic() functions.
>
> Finally, the dynamic objects' structures are generic. The respective
> klp_allocate_object_dynamic() and klp_free_object_dynamic() can
> be implemented here. On the other hand, klp_free_func_dynamic()
> is empty. It must be updated when a particular dynamic
> klp_func_type is introduced.
>
> Signed-off-by: Jason Baron <jbaron@akamai.com>
> [pmladek@suse.com: Converted into a generic API]
> Signed-off-by: Petr Mladek <pmladek@suse.com>
> Cc: Josh Poimboeuf <jpoimboe@redhat.com>
> Cc: Jessica Yu <jeyu@kernel.org>
> Cc: Jiri Kosina <jikos@kernel.org>
> Cc: Miroslav Benes <mbenes@suse.cz>
> ---
> include/linux/livepatch.h | 37 +++++++++++-
> kernel/livepatch/core.c | 139 ++++++++++++++++++++++++++++++++++++++++------
> 2 files changed, 159 insertions(+), 17 deletions(-)
>
> diff --git a/include/linux/livepatch.h b/include/linux/livepatch.h
> index e5db2ba7e2a5..21cad200f949 100644
> --- a/include/linux/livepatch.h
> +++ b/include/linux/livepatch.h
> @@ -35,12 +35,22 @@
> #define KLP_UNPATCHED 0
> #define KLP_PATCHED 1
>
> +/*
> + * Function type is used to distinguish dynamically allocated structures
> + * and limit some operations.
> + */
> +enum klp_func_type {
> + KLP_FUNC_ANY = -1, /* Substitute any type */
> + KLP_FUNC_ORIGINAL = 0, /* Original statically defined structure */
Wouldn't KLP_FUNC_STATIC be better? KLP_FUNC_ORIGINAL confused me couple
of times.
Miroslav
next prev parent reply other threads:[~2018-01-31 15:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 16:01 PATCH v6 0/6] livepatch: Atomic replace feature Petr Mladek
2018-01-25 16:01 ` PATCH v6 1/6] livepatch: Use lists to manage patches, objects and functions Petr Mladek
2018-01-25 16:01 ` PATCH v6 2/6] livepatch: Free only structures with initialized kobject Petr Mladek
2018-02-01 14:25 ` Joe Lawrence
2018-01-25 16:02 ` PATCH v6 3/6] livepatch: Initial support for dynamic structures Petr Mladek
2018-01-31 15:39 ` Miroslav Benes [this message]
2018-02-05 10:33 ` Petr Mladek
2018-01-25 16:02 ` PATCH v6 4/6] livepatch: Allow to unpatch only functions of the given type Petr Mladek
2018-01-31 15:42 ` Miroslav Benes
2018-01-25 16:02 ` PATCH v6 5/6] livepatch: Support separate list for replaced patches Petr Mladek
2018-01-31 16:19 ` Miroslav Benes
2018-01-25 16:02 ` PATCH v6 6/6] livepatch: Add atomic replace Petr Mladek
2018-01-26 4:27 ` Jason Baron
2018-01-26 9:09 ` Petr Mladek
2018-01-26 10:33 ` Evgenii Shatokhin
2018-01-31 21:55 ` Josh Poimboeuf
2018-02-01 8:15 ` Evgenii Shatokhin
2018-02-01 13:49 ` Miroslav Benes
2018-02-05 14:15 ` Petr Mladek
2018-02-01 13:49 ` PATCH v6 0/6] livepatch: Atomic replace feature Miroslav Benes
2018-02-01 14:28 ` Joe Lawrence
2018-02-01 15:08 ` Miroslav Benes
2018-02-01 15:18 ` Josh Poimboeuf
2018-02-01 15:51 ` 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=alpine.LSU.2.21.1801311637140.7649@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=eshatokhin@virtuozzo.com \
--cc=jbaron@akamai.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.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
all inboxes | Powered by JetHome®