LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Miroslav Benes <mbenes@suse.cz>
To: Petr Mladek <pmladek@suse.com>
Cc: Jiri Kosina <jikos@kernel.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	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 v3 0/2] livepatch: Allocate and free shadow variables more safely
Date: Tue, 17 Apr 2018 13:21:25 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.21.1804171320480.12184@pobox.suse.cz> (raw)
In-Reply-To: <20180416113647.25288-1-pmladek@suse.com>

On Mon, 16 Apr 2018, Petr Mladek wrote:

> Nikolai started to use shadow variables and found that list_head
> is not initialized correctly using the existing API.
> 
> The problem is that LIST_HEAD_INIT() set pointers to itself.
> klp_shadow_alloc() then copies these pointers to another location.
> 
> It would be possible to solve this by a late initialization. But
> this does not work well with klp_shadow_get_or_alloc(). Also this
> behavior is error prone. Note that list_head might be hidden in
> another structure, for example mutex.
> 
> I suggest to change the API and allow to initialize the shadow
> variables using a custom callback. I think that we have already
> talked about this but we decided to go the easier way. It seems
> that it was a bad decision.
> 
> I send also patch that add a symmetric callback to the klp_shadow_free()
> functions. It might be handy especially for klp_shadow_free_all().
> 
> 
> Changes against v2:
> 
>   + Use pr_err() instead of WARN() when ctor() fails [Josh]
>   + Some typos [Mirek]
> 
> 
> Changes against v1:
> 
>   + Rename init/free callbacks to ctor/dtor
>   + Misc update of comments and commit messages
>   + Fix sizeof() in the sample code in shadow-vars.txt
> 
> 
> Petr Mladek (2):
>   livepatch: Initialize shadow variables safely by a custom callback
>   livepatch: Allow to call a custom callback when freeing shadow
>     variables
> 
>  Documentation/livepatch/shadow-vars.txt   |  41 ++++++++----
>  include/linux/livepatch.h                 |  19 ++++--
>  kernel/livepatch/shadow.c                 | 108 ++++++++++++++++++++----------
>  samples/livepatch/livepatch-shadow-fix1.c |  43 +++++++++---
>  samples/livepatch/livepatch-shadow-fix2.c |  33 ++++-----
>  5 files changed, 163 insertions(+), 81 deletions(-)

Acked-by: Miroslav Benes <mbenes@suse.cz>

M

  parent reply	other threads:[~2018-04-17 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 11:36 Petr Mladek
2018-04-16 11:36 ` [PATCH v3 1/2] livepatch: Initialize shadow variables safely by a custom callback Petr Mladek
2018-04-16 11:36 ` [PATCH v3 2/2] livepatch: Allow to call a custom callback when freeing shadow variables Petr Mladek
2018-04-16 19:57 ` [PATCH v3 0/2] livepatch: Allocate and free shadow variables more safely Josh Poimboeuf
2018-04-17 11:21 ` Miroslav Benes [this message]
2018-04-17 11:44 ` Jiri Kosina

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.1804171320480.12184@pobox.suse.cz \
    --to=mbenes@suse.cz \
    --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=nstange@suse.de \
    --cc=pmladek@suse.com \
    --subject='Re: [PATCH v3 0/2] livepatch: Allocate and free shadow variables more safely' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).