Displaying 3 results from an estimated 3 matches for "fail_update".
Did you mean:
daily_update
2017 Oct 04
1
[RFC v3 20/27] x86/ftrace: Adapt function tracing for PIE support
...g ip, unsigned const char *old_code,
{
int ret;
- ret = add_break(ip, old_code);
+ ret = add_break(ip, old_code, MCOUNT_RELINSN_SIZE);
if (ret)
goto out;
run_sync();
- ret = add_update_code(ip, new_code);
+ ret = add_update_code(ip, new_code, MCOUNT_RELINSN_SIZE);
if (ret)
goto fail_update;
@@ -670,7 +726,7 @@ static unsigned char *ftrace_jmp_replace(unsigned long ip, unsigned long addr)
/* Jmp not a call (ignore the .e8) */
calc.e8 = 0xe9;
- calc.offset = ftrace_calc_offset(ip + MCOUNT_INSN_SIZE, addr);
+ calc.offset = ftrace_calc_offset(ip + MCOUNT_RELINSN_SIZE, addr);...
2017 Oct 04
28
x86: PIE support and option to extend KASLR randomization
These patches make the changes necessary to build the kernel as Position
Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below
the top 2G of the virtual address space. It allows to optionally extend the
KASLR randomization range from 1G to 3G.
Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler
changes, PIE support and KASLR in general. Thanks to
2017 Oct 04
28
x86: PIE support and option to extend KASLR randomization
These patches make the changes necessary to build the kernel as Position
Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below
the top 2G of the virtual address space. It allows to optionally extend the
KASLR randomization range from 1G to 3G.
Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler
changes, PIE support and KASLR in general. Thanks to