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: [PATCHv4 0/3] Kernel Live Patching
Date: Wed, 26 Nov 2014 18:00:54 +0900 [thread overview]
Message-ID: <547596C6.2050303@hitachi.com> (raw)
In-Reply-To: <1416935709-404-1-git-send-email-sjenning@redhat.com>
(2014/11/26 2:15), Seth Jennings wrote:
> Note to Steve:
> Masami's IPMODIFY patch is heading for -next via your tree. Once it arrives,
> I'll rebase and make the change to set IPMODIFY. Do not pull this for -next
> yet. This version (v4) is for review and gathering acks.
BTW, as we discussed IPMODIFY is an exclusive flag. So if we allocate ftrace_ops
for each function in each patch, it could be conflict each other.
Maybe we need to have another ops hashtable to find such conflict and new
handler to handle it.
Thank you,
--
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-26 9:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 17:15 [PATCHv4 0/3] Kernel Live Patching Seth Jennings
2014-11-25 17:15 ` [PATCHv4 1/3] kernel: add TAINT_LIVEPATCH Seth Jennings
2014-11-25 17:15 ` [PATCHv4 2/3] kernel: add support for live patching Seth Jennings
2014-11-26 9:05 ` Masami Hiramatsu
2014-11-26 13:37 ` Jiri Slaby
2014-11-26 14:19 ` Miroslav Benes
2014-11-26 15:40 ` Josh Poimboeuf
2014-12-01 13:31 ` Miroslav Benes
2014-12-01 17:07 ` Josh Poimboeuf
2014-12-02 12:24 ` Miroslav Benes
2014-11-28 17:07 ` Petr Mladek
2014-11-28 17:14 ` [PATCH] livepatch: clean up klp_find_object_module() usage: was: " Petr Mladek
2014-12-01 12:08 ` Miroslav Benes
2014-12-01 12:40 ` Petr Mladek
2014-11-28 17:19 ` [PATCH] livepatch: do relocation when initializing the patch: " Petr Mladek
2014-12-03 10:00 ` Miroslav Benes
2014-11-25 17:15 ` [PATCHv4 3/3] samples: add sample live patching module Seth Jennings
2014-11-27 17:05 ` Petr Mladek
2014-12-01 17:11 ` Seth Jennings
2014-11-25 19:26 ` [PATCHv4 0/3] Kernel Live Patching Jiri Kosina
2014-11-25 22:10 ` Seth Jennings
2014-11-25 22:22 ` Jiri Kosina
2014-11-26 9:00 ` Masami Hiramatsu [this message]
2014-11-26 9:18 ` Jiri Kosina
2014-11-26 9:26 ` Jiri Kosina
2014-11-26 15:27 ` Josh Poimboeuf
2014-11-27 10:06 ` Masami Hiramatsu
2014-11-27 10:52 ` Petr Mladek
2014-11-28 2:21 ` Masami Hiramatsu
2014-11-27 6:12 ` Masami Hiramatsu
2014-11-26 15:55 ` Josh Poimboeuf
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=547596C6.2050303@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