summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorSatoshi Oshima <soshima@redhat.com>2006-05-21 00:00:21 +0200
committerLinus Torvalds <torvalds@g5.osdl.org>2006-05-21 21:59:21 +0200
commitdc49e3445aa703eb7fd33c7ddb7e4a7bbcf06d30 (patch)
treeeb164ad61b92f2df2ffab9628adffe06e635c8e2 /lib
parent[PATCH] i386 kdump boot cpu physical apicid fix (diff)
downloadlinux-dc49e3445aa703eb7fd33c7ddb7e4a7bbcf06d30.tar.xz
linux-dc49e3445aa703eb7fd33c7ddb7e4a7bbcf06d30.zip
[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>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions