From: Joe Lawrence <joe.lawrence@redhat.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>, Petr Mladek <pmladek@suse.com>
Cc: Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
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 15:43:01 -0400 [thread overview]
Message-ID: <acd1592a-3f0d-c515-b90f-b1ed9694204b@redhat.com> (raw)
In-Reply-To: <20180314192857.yfdk2uwn4okuzlfh@treble>
On 03/14/2018 03:28 PM, Josh Poimboeuf wrote:
> On Tue, Mar 13, 2018 at 04:54:47PM +0100, Petr Mladek wrote:
>
>> 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?
Compiles ok w/o it, so shouldn't be 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?
>
struct klp_shadow {
struct hlist_node node;
struct rcu_head rcu_head;
void *obj;
unsigned long id;
char data[]; << not a pointer
};
In the past, this function would allocate the klp_shadow struct size
accordingly, then memcpy in its data contents. This patch pushes the
responsibility of data initialization out to the init_func().
-- Joe
next prev parent reply other threads:[~2018-03-14 19:43 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
2018-03-14 19:43 ` Joe Lawrence [this message]
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=acd1592a-3f0d-c515-b90f-b1ed9694204b@redhat.com \
--to=joe.lawrence@redhat.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=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®