Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1469541

Re: livepatch/kprobes incompatibility

Show all headers | View raw

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>

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

livepatch/kprobes incompatibility Jessica Yu <jeyu@redhat.com> - 2016-08-24 03:20 +0200
  Re: livepatch/kprobes incompatibility Petr Mladek <pmladek@suse.com> - 2016-08-24 11:50 +0200
    Re: livepatch/kprobes incompatibility Masami Hiramatsu <mhiramat@kernel.org> - 2016-08-24 17:30 +0200
    Re: livepatch/kprobes incompatibility Josh Poimboeuf <jpoimboe@redhat.com> - 2016-08-25 18:10 +0200
  Re: livepatch/kprobes incompatibility Masami Hiramatsu <mhiramat@kernel.org> - 2016-08-24 17:20 +0200

csiph-web