From: Miroslav Benes <mbenes@suse.cz>
To: Petr Mladek <pmladek@suse.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
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
Subject: Re: [PATCH v7 3/7] livepatch: Initial support for dynamic structures
Date: Fri, 9 Feb 2018 11:06:11 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.1802081643010.18225@pobox.suse.cz> (raw)
In-Reply-To: <20180206103424.10829-4-pmladek@suse.com>
On Tue, 6 Feb 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>
This patch introduces klp_get_or_add_object(), but it is not used here.
One of the later patches adds its call site. GCC warns about this. I like
it being introduced here, because it belongs to the patch. Someone may
complain though.
Also klp_free_objects() is not declared as static and sparse complains
about it. Petr, you can make it static here and drop the keyword later.
Otherwise it looks good.
Acked-by: Miroslav Benes <mbenes@suse.cz>
Miroslav
next prev parent reply other threads:[~2018-02-09 10:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 10:34 [PATCH v7 0/7] livepatch: Atomic replace feature Petr Mladek
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 [this message]
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=alpine.LSU.2.21.1802081643010.18225@pobox.suse.cz \
--to=mbenes@suse.cz \
--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=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®