mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Seth Jennings <sjenning@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	Jiri Kosina <jkosina@suse.cz>, Vojtech Pavlik <vojtech@suse.cz>,
	Steven Rostedt <rostedt@goodmis.org>,
	Petr Mladek <pmladek@suse.cz>, Miroslav Benes <mbenes@suse.cz>,
	Christoph Hellwig <hch@infradead.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Andy Lutomirski <luto@amacapital.net>,
	live-patching@vger.kernel.org, x86@kernel.org, kpatch@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 0/3] Kernel Live Patching
Date: Fri, 21 Nov 2014 11:44:46 +0900	[thread overview]
Message-ID: <546EA71E.6000004@hitachi.com> (raw)
In-Reply-To: <1416522580-5593-1-git-send-email-sjenning@redhat.com>

Hi Seth,

(2014/11/21 7:29), Seth Jennings wrote:
> Summary:
> 
> This patchset implements an ftrace-based mechanism and kernel interface for
> doing live patching of kernel and kernel module functions.  It represents the
> greatest common functionality set between kpatch [1] and kGraft [2] and can
> accept patches built using either method.  This solution was discussed in the
> Live Patching Mini-conference at LPC 2014 [3].
> 
> The model consists of a live patching "core" that provides an interface for
> other "patch" kernel modules to register patches with the core.
> 
> Patch modules contain the new function code and create an klp_patch structure
> containing the required data about what functions to patch, where the new code
> for each patched function resides, and in which kernel object (vmlinux or
> module) the function to be patch resides.  The patch module then invokes the
> klp_register_patch() function to register with the core, then klp_enable_patch()
> to have the core redirect the execution paths using ftrace.
> 
> An example patch module can be found here:
> https://github.com/spartacus06/livepatch/blob/master/patch/patch.c

Hmm, I think we should import this example under samples/livepatch/ or
tools/testing/selftests/livepatch/ for self testing, so that others
can easily see what will happen. :)

Thank you,


-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



      parent reply	other threads:[~2014-11-21  2:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 22:29 Seth Jennings
2014-11-20 22:29 ` [PATCHv3 1/3] kernel: add TAINT_LIVEPATCH Seth Jennings
2014-11-20 22:29 ` [PATCHv3 2/3] kernel: add support for live patching Seth Jennings
2014-11-21  0:22   ` Jiri Kosina
2014-11-21 14:44     ` Miroslav Benes
2014-11-21 15:00       ` Josh Poimboeuf
2014-11-21 15:46         ` Miroslav Benes
2014-11-21 16:13           ` Seth Jennings
2014-11-21 15:21     ` Josh Poimboeuf
2014-11-21 15:27       ` Jiri Kosina
2014-11-21 15:35         ` Josh Poimboeuf
2014-11-21 16:40     ` Seth Jennings
2014-11-21 17:35       ` Jiri Slaby
2014-11-21 18:29         ` Seth Jennings
2014-11-21 17:53       ` Andy Lutomirski
2014-11-21  2:39   ` Masami Hiramatsu
2014-11-25 16:39     ` Petr Mladek
2014-11-25 16:52       ` Steven Rostedt
2014-11-25 17:04         ` Petr Mladek
2014-11-25 17:16           ` Steven Rostedt
2014-11-25 19:29             ` Jiri Kosina
2014-12-03  8:09               ` Masami Hiramatsu
2014-11-24 11:13   ` Thomas Gleixner
2014-11-24 13:21     ` Jiri Kosina
2014-11-24 13:26       ` Thomas Gleixner
2014-11-24 13:31         ` Vojtech Pavlik
2014-11-24 14:25           ` Masami Hiramatsu
2014-11-24 13:31         ` Jiri Kosina
2014-11-24 13:23     ` Vojtech Pavlik
2014-11-24 13:24     ` Josh Poimboeuf
2014-11-24 13:27     ` Masami Hiramatsu
2014-11-20 22:29 ` [PATCHv3 3/3] kernel: add sysfs documentation " Seth Jennings
2014-11-21  2:49   ` Masami Hiramatsu
2014-11-21 16:41     ` Seth Jennings
2014-11-21  2:44 ` Masami Hiramatsu [this message]

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=546EA71E.6000004@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=jkosina@suse.cz \
    --cc=jpoimboe@redhat.com \
    --cc=kpatch@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mbenes@suse.cz \
    --cc=pmladek@suse.cz \
    --cc=rostedt@goodmis.org \
    --cc=sjenning@redhat.com \
    --cc=vojtech@suse.cz \
    --cc=x86@kernel.org \
    /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

Powered by JetHome