On Fri, 16 Jan 2015 17:41:58 +0100 (CET)
Jiri Kosina wrote:
> On Fri, 16 Jan 2015, Steven Rostedt wrote:
>
> > Instead, make live kernel patching fail to load if fentry isn't
> > supported. IOW, instead of ftrace_ipmodify_supported, have a
> > live_kernel_patching_supported that could be based
On Fri, 16 Jan 2015, Steven Rostedt wrote:
> Instead, make live kernel patching fail to load if fentry isn't
> supported. IOW, instead of ftrace_ipmodify_supported, have a
> live_kernel_patching_supported that could be based on fentry being used
> or not.
I can live with that, we are handling
On Thu, 15 Jan 2015 10:50:07 +0100 (CET)
Jiri Kosina wrote:
> Using IPMODIFY needs to be allowed only with compilers which are
> guaranteed to generate function prologues compatible with function
> redirection through changing instruction pointer in saved regs.
That's actually not true.
Sorry
Using IPMODIFY needs to be allowed only with compilers which are
guaranteed to generate function prologues compatible with function
redirection through changing instruction pointer in saved regs.
For example changing regs->ip on x86_64 in cases when gcc is using mcount
(and not fentry) is not a
4 matches
Mail list logo
