From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Joe Lawrence <joe.lawrence@redhat.com>,
Jessica Yu <jeyu@kernel.org>, Nicolai Stange <nstange@suse.de>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] livepatch: Initialize shadow variables by init function safely
Date: Wed, 14 Mar 2018 14:28:57 -0500 [thread overview]
Message-ID: <20180314192857.yfdk2uwn4okuzlfh@treble> (raw)
In-Reply-To: <20180313155448.1998-2-pmladek@suse.com>
On Tue, Mar 13, 2018 at 04:54:47PM +0100, Petr Mladek wrote:
> The existing API allows to pass a sample data to initialize the shadow
> data. It works well when the data are position independent. But it fails
> miserably when we need to set a pointer to the shadow structure itself.
>
> Unfortunately, we might need to initialize the pointer surprisingly
> often because of struct list_head. It is even worse because the list
> might be hidden in other common structures, for example, struct mutex,
> struct wait_queue_head.
Can you provide a specific example in the changelog of where this was
needed?
> This patch makes the API more safe. A custom init function and data
> are passed to klp_shadow_*alloc() functions instead of the sample data.
>
> Note that the init_data are not longer a template for the shadow->data.
> It might point to any data that might be necessary when the init
> function is called.
>
> In addition, the newly allocated shadow structure is initialized
> only when it is really used.
I don't understand this sentence. It makes it sound like the init
function is called when you do klp_shadow_get(). However, looking at
the code, the init function is always called after allocation.
> For this, the init function must be
> called under klp_shadow_lock. On one hand, this adds a risk of
> ABBA deadlocks. On the other hand, it allows to do some operations
> safely. For example, we could add the new structure into an
> existing list.
> diff --git a/include/linux/livepatch.h b/include/linux/livepatch.h
> index 4754f01c1abb..fc7c64ce0992 100644
> --- a/include/linux/livepatch.h
> +++ b/include/linux/livepatch.h
> @@ -186,11 +186,20 @@ static inline bool klp_have_reliable_stack(void)
> IS_ENABLED(CONFIG_HAVE_RELIABLE_STACKTRACE);
> }
>
> +struct klp_shadow;
Why is this forward struct declaration needed?
> @@ -150,6 +145,23 @@ static void *__klp_shadow_get_or_alloc(void *obj, unsigned long id, void *data,
> goto exists;
> }
>
> + new_shadow->obj = obj;
> + new_shadow->id = id;
> +
> + if (init_func) {
> + int err;
> +
> + err = init_func(obj, new_shadow->data, init_data);
Am I hallucinating, or will new_shadow->data always be NULL? How did it
even work before?
--
Josh
next prev parent reply other threads:[~2018-03-14 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 15:54 [PATCH 0/2] livepatch: Allocate and free shadow variables more safely Petr Mladek
2018-03-13 15:54 ` [PATCH 1/2] livepatch: Initialize shadow variables by init function safely Petr Mladek
2018-03-14 19:27 ` Joe Lawrence
2018-03-14 19:44 ` Josh Poimboeuf
2018-04-04 13:08 ` Petr Mladek
2018-03-14 19:28 ` Josh Poimboeuf [this message]
2018-03-14 19:43 ` Joe Lawrence
2018-03-14 20:22 ` Josh Poimboeuf
2018-03-21 12:55 ` Miroslav Benes
2018-03-13 15:54 ` [PATCH 2/2] livepatch: Allow to unregister or free shadow data using a custom function Petr Mladek
2018-03-14 19:32 ` Josh Poimboeuf
2018-03-21 13:05 ` 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=20180314192857.yfdk2uwn4okuzlfh@treble \
--to=jpoimboe@redhat.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=nstange@suse.de \
--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®