Displaying 3 results from an estimated 3 matches for "add_update_cod".
Did you mean:
add_update_code
2017 Oct 04
1
[RFC v3 20/27] x86/ftrace: Adapt function tracing for PIE support
...race_expected = nop;
- if (memcmp(&ins[1], &nop[1], MCOUNT_INSN_SIZE - 1) != 0)
+ if (memcmp(&ins[1], &nop[1], size - 1) != 0)
return -EINVAL;
}
@@ -428,30 +481,33 @@ static int remove_breakpoint(struct dyn_ftrace *rec)
return ftrace_write(ip, nop, 1);
}
-static int add_update_code(unsigned long ip, unsigned const char *new)
+static int add_update_code(unsigned long ip, unsigned const char *new,
+ unsigned int size)
{
/* skip breakpoint */
ip++;
new++;
- return ftrace_write(ip, new, MCOUNT_INSN_SIZE - 1);
+ return ftrace_write(ip, new, size - 1);
}
static int...
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