Satoshi Oshima dc49e3445a [PATCH] kprobes: bad manipulation of 2 byte opcode on x86_64 ... Problem: If we put a probe onto a callq instruction and the probe is executed, kernel panic of Bad RIP value occurs. Root cause: If resume_execution() found 0xff at first byte of p->ainsn.insn, it must check the _second_ byte. But current resume_execution check _first_ byte again. I changed it checks second byte of p->ainsn.insn. Kprobes on i386 don't have this problem, because the implementation is a little bit different from x86_64. Cc: Andi Kleen <ak@muc.de> Signed-off-by: Satoshi Oshima <soshima@redhat.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		2006-05-21 12:59:21 -07:00
..
boot
crypto
ia32	[PATCH] x86_64: Add compat_sys_vmsplice and use it in x86-64	2006-05-01 18:17:43 -07:00
kernel	[PATCH] kprobes: bad manipulation of 2 byte opcode on x86_64	2006-05-21 12:59:21 -07:00
lib
mm	[PATCH] x86_64: Fix memory hotadd heuristics	2006-05-16 07:59:31 -07:00
oprofile
pci
defconfig
Kconfig
Kconfig.debug
Makefile