From: Masami Hiramatsu <mhiramat@kernel.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Jessica Yu <jeyu@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: livepatch/kprobes incompatibility
Date: Thu, 25 Aug 2016 00:23:19 +0900 [thread overview]
Message-ID: <20160825002319.43769195b85c943981d4ec8b@kernel.org> (raw)
In-Reply-To: <20160824093959.GG4866@pathway.suse.cz>
On Wed, 24 Aug 2016 11:39:59 +0200
Petr Mladek <pmladek@suse.com> wrote:
> Well, there is one more problem. We should also warn when a kprobe
> is not longer accessible because the function call is redirected
> by a livepatch. My last notes about it are:
>
> + worked on the check for lost Kprobes; decided that only Kprobe
> knows about all probes and need to be informed about patching;
> added KPROBE_FLAG_PATCHED and its handling; it will be used
> by a fake probe that will just signalize that the function is
> patched; added helper functions that will register and unregister
> that fake probe; the patchset still needs some clean up before
> sending
I think the warning is acceptable but no need to update by flag,
since the livepatch can be removed and kprobes can come back again.
Moreover, at the lower level like kprobes, user might want to use
it for monitoring that the patched code is actually not executed,
like security inspection.
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2016-08-24 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 1:13 Jessica Yu
2016-08-24 9:39 ` Petr Mladek
2016-08-24 15:23 ` Masami Hiramatsu [this message]
2016-08-25 16:08 ` Josh Poimboeuf
2016-08-24 15:16 ` 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=20160825002319.43769195b85c943981d4ec8b@kernel.org \
--to=mhiramat@kernel.org \
--cc=jeyu@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
Powered by JetHome