On Wed, 8 May 2019 13:30:22 +0900
Masami Hiramatsu wrote:
> > To solve this, an int3_emulate_call() is created for x86_64 to allow
> > ftrace on x86_64 to emulate the call to ftrace_regs_caller() which will
> > make sure all the registered handlers to that function are still called.
> > And this
Steven Rostedt writes:
> [
> This is the non-RFC version.
>
> It went through and passed all my tests. If there's no objections
> I'm going to include this in my pull request. I still have patches
> in my INBOX that may still be included, so I need to run those through
> my tests as
On Tue, 07 May 2019 21:55:59 -0400
Steven Rostedt wrote:
>
> [
> This is the non-RFC version.
>
> It went through and passed all my tests. If there's no objections
> I'm going to include this in my pull request. I still have patches
> in my INBOX that may still be included, so I need
[
This is the non-RFC version.
It went through and passed all my tests. If there's no objections
I'm going to include this in my pull request. I still have patches
in my INBOX that may still be included, so I need to run those through
my tests as well, so a pull request wont be
Nicolai Stange discovered that Live Kernel Patching can have unforseen
consequences if tracing is enabled when there are functions that are
patched. The reason being, is that Live Kernel patching is built on top
of ftrace, which will have the patched functions call the live kernel
trampoline
5 matches
Mail list logo