From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Seth Jennings <sjenning@redhat.com>,
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 2/3] kernel: add support for live patching
Date: Mon, 24 Nov 2014 22:27:55 +0900 [thread overview]
Message-ID: <5473325B.7070609@hitachi.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1411241209050.6439@nanos>
(2014/11/24 20:13), Thomas Gleixner wrote:
> On Thu, 20 Nov 2014, Seth Jennings wrote:
>> This commit introduces code for the live patching core. It 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 and
>> kgraft and can accept patches built using either method.
>>
>> This first version does not implement any consistency mechanism that
>> ensures that old and new code do not run together. In practice, ~90% of
>> CVEs are safe to apply in this way, since they simply add a conditional
>> check. However, any function change that can not execute safely with
>> the old version of the function can _not_ be safely applied in this
>> version.
>
> To be honest this sounds frightening.
>
I see. This is just a minimal one. We'll add several consistency
mechanisms :).
> How is determined whether a change can be applied w/o a consistency
> mechanism or not?
I guess the following cases are possible to be applied.
- the code itself ensures consistency (e.g. in a critical section)
or,
- the patch just changes one place (e.g. add an if branch) and
only depends on the local context (e.g. local variables), and
doesn't called in a loop, so that old- and new-version of the
function can co-exist.
Thank you,
>
> Thanks,
>
> tglx
>
>
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2014-11-24 13:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 22:29 [PATCHv3 0/3] Kernel Live Patching 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 [this message]
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 ` [PATCHv3 0/3] Kernel Live Patching Masami Hiramatsu
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=5473325B.7070609@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=tglx@linutronix.de \
--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