b92c4f922b
This patch uses MAX_REG_NR consistently to refer to the register file size. FRAME_SIZE isn't sufficient because on x86_64, it is smaller than the ptrace register file size. MAX_REG_NR was introduced as a consistent way to get the number of registers, but wasn't used everywhere it should be. When this causes a problem, it makes PTRACE_SETREGS fail on x86_64 because of a corrupted segment register value in the known-good register file. The patch also adds a register dump at that point in case there are any future problems here. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
---|---|---|
.. | ||
drivers | ||
include | ||
skas | ||
sys-i386 | ||
sys-x86_64 | ||
aio.c | ||
elf_aux.c | ||
execvp.c | ||
file.c | ||
helper.c | ||
irq.c | ||
main.c | ||
Makefile | ||
mem.c | ||
process.c | ||
sigio.c | ||
signal.c | ||
start_up.c | ||
time.c | ||
tls.c | ||
trap.c | ||
tt.c | ||
tty_log.c | ||
tty.c | ||
uaccess.c | ||
umid.c | ||
user_syms.c | ||
util.c |