linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miroslav Benes <mbenes@suse.cz>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Jessica Yu <jeyu@redhat.com>, Jiri Kosina <jikos@kernel.org>,
	Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v6] livepatch: introduce shadow variable API
Date: Wed, 13 Sep 2017 14:00:37 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.21.1709131358120.27762@san.suse.cz> (raw)
In-Reply-To: <1504211861-19899-2-git-send-email-joe.lawrence@redhat.com>

On Thu, 31 Aug 2017, Joe Lawrence wrote:

> Add exported API for livepatch modules:
> 
>   klp_shadow_get()
>   klp_shadow_alloc()
>   klp_shadow_get_or_alloc()
>   klp_shadow_free()
>   klp_shadow_free_all()
> 
> that implement "shadow" variables, which allow callers to associate new
> shadow fields to existing data structures.  This is intended to be used
> by livepatch modules seeking to emulate additions to data structure
> definitions.
> 
> See Documentation/livepatch/shadow-vars.txt for a summary of the new
> shadow variable API, including a few common use cases.
> 
> See samples/livepatch/livepatch-shadow-* for example modules that
> demonstrate shadow variables.
> 
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>

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

I'd wait for Petr's review.

Thanks,
Miroslav

  parent reply	other threads:[~2017-09-13 12:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 20:37 [PATCH v6] Livepatch shadow variables Joe Lawrence
2017-08-31 20:37 ` [PATCH v6] livepatch: introduce shadow variable API Joe Lawrence
2017-09-12 16:20   ` Josh Poimboeuf
2017-09-12 22:11     ` Joe Lawrence
2017-09-13 13:45       ` Jiri Kosina
2017-09-13 12:00   ` Miroslav Benes [this message]
2017-09-14 21:08 ` [PATCH v6] Livepatch shadow variables Jiri Kosina
2017-09-25 15:45   ` Petr Mladek

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.1709131358120.27762@san.suse.cz \
    --to=mbenes@suse.cz \
    --cc=jeyu@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).