Kprobes: Allow/deny probes on int3/breakpoint instruction?
PATCH 1/1 Kprobes: Allow/deny probes on int3/breakpoint instruction?
Hi,
Kprobes did an improper exit when a probe is inserted on an int3 instruction. In case of normal execution of int3/breakpoint instruction, it oops!. Probe on an int3 instruction was not handled properly by the kprobes, it generated faults after oops! doing an improper exit with holding the lock. This fix employes a bit different method to handle probe on an int3/breakpoint instruction.
On execution of an int3/breakpoint instruction (placed by kprobe), kprobes_handler() is called which sets it for single stepping in-line(it does not matter whether we single step out-of-line/inline since the single stepping instruction is same). Now it single steps on int3/breakpoint instruction here, entering kprobes_handler() once again. Kprobes now check's the status that it is single stepping and avoids the recursion. It runs down through the trap handler and oops messages is seen on the console since it executed int3/breakpoint instruction. Here the kprobes single stepping handler never gets called.
Is this behaviour acceptable ? Or should we avoid putting probes on an int3 /breakpoint instruction ? How should it handle such situations? Below is the patch to allow probes on an int3/breakpoint instruction.
This patch fixes the above problem by doing a proper exit while avoiding recursion.
Any pointers/suggestions on the above issues will be helpful.
---
linux-2.6.12-rc1-prasanna/arch/i386/kernel/kprobes.c | 12 +++++++++++- linux-2.6.12-rc1-prasanna/arch/ppc64/kernel/kprobes.c | 12 +++++++++++- linux-2.6.12-rc1-prasanna/arch/sparc64/kernel/kprobes.c | 16 ++++++++++++++-- linux-2.6.12-rc1-prasanna/arch/x86_64/kernel/kprobes.c | 13 +++++++++++-- 4 files changed, 47 insertions(+), 6 deletions(-)
arch/i386/kernel/kprobes.c renamed from arch/i386/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -1
@@ -84,7 +84,11 @@ static inline void prepare_singlestep(st { regs->eflags |=TF_MASK ; regs->eflags &= ~IF_MASK ; - regs->eip = (unsigned long )&p->ainsn.insn; +/*single step inline if the instruction is an int3*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->eip = (unsigned long )p->addr; +else + regs->eip = (unsigned long )&p->ainsn.insn; }/*
@@ -117,6 +121,12 @@ static int kprobe_handler(struct pt_regsDisarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->eflags &= ~TF_MASK ; + regs->eflags |= kprobe_saved_eflags; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/x86_64/kernel/kprobes.c renamed from arch/x86_64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -2
@@ -108,8 +108,11 @@ static void prepare_singlestep(struct kp { regs->eflags |=TF_MASK ; regs->eflags &= ~IF_MASK ; - - regs->rip = (unsigned long )p->ainsn.insn; +/*single step inline if the instruction is an int3*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->rip = (unsigned long )p->addr; +else + regs->rip = (unsigned long )p->ainsn.insn; }/*
@@ -131,6 +134,12 @@ int kprobe_handler(struct pt_regs *regs)Disarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->eflags &= ~TF_MASK ; + regs->eflags |= kprobe_saved_eflags; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/ppc64/kernel/kprobes.c renamed from arch/ppc64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -1
@@ -71,7 +71,11 @@ static inline void disarm_kprobe(structstatic inline void prepare_singlestep (struct kprobe *p,struct pt_regs *regs) { regs->msr |=MSR_SE ; - regs->nip = (unsigned long )&p->ainsn.insn; +/*single step inline if it a breakpoint instruction*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->nip = (unsigned long )p->addr; +else + regs->nip = (unsigned long )&p->ainsn.insn; }static inline int kprobe_handler (struct pt_regs *regs)
@@ -89,6 +93,12 @@ static inline int kprobe_handler(structDisarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->msr &= ~MSR_SE ; + regs->msr |= kprobe_saved_msr; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/sparc64/kernel/kprobes.c renamed from arch/sparc64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +14 -2
@@ -68,8 +68,14 @@ static inline void prepare_singlestep(st current_kprobe_orig_tstate_pil = (regs->tstate &TSTATE_PIL ); regs->tstate |=TSTATE_PIL ; - regs->tpc = (unsigned long ) &p->ainsn.insn[0 ]; - regs->tnpc = (unsigned long ) &p->ainsn.insn[1 ]; +/*single step inline, if it a breakpoint instruction*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) { + regs->tpc = (unsigned long ) p->addr; + regs->tnpc = current_kprobe_orig_tnpc; + }else { + regs->tpc = (unsigned long ) &p->ainsn.insn[0 ]; + regs->tnpc = (unsigned long ) &p->ainsn.insn[1 ]; + } }static inline void disarm_kprobe (struct kprobe *p,struct pt_regs *regs)
@@ -97,6 +103,12 @@ static int kprobe_handler(struct pt_regs*/ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->tstate = ((regs->tstate & ~TSTATE_PIL ) | + current_kprobe_orig_tstate_pil); +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
_
Thanks
Prasanna
Signature · 5 lines
Prasanna S Panchamukhi Linux Technology Center India Software Labs, IBM Bangalore Ph: 91-80-25044636 <[email protected]>
PATCH 1/1 Kprobes: Allow/deny probes on int3/breakpoint instruction?
Hi,
Kprobes did an improper exit when a probe is inserted on an int3 instruction. In case of normal execution of int3/breakpoint instruction, it oops!. Probe on an int3 instruction was not handled properly by the kprobes, it generated faults after oops! doing an improper exit with holding the lock. This fix employes a bit different method to handle probe on an int3/breakpoint instruction.
On execution of an int3/breakpoint instruction (placed by kprobe), kprobes_handler() is called which sets it for single stepping in-line(it does not matter whether we single step out-of-line/inline since the single stepping instruction is same). Now it single steps on int3/breakpoint instruction here, entering kprobes_handler() once again. Kprobes now check's the status that it is single stepping and avoids the recursion. It runs down through the trap handler and oops messages is seen on the console since it executed int3/breakpoint instruction. Here the kprobes single stepping handler never gets called.
Is this behaviour acceptable ? Or should we avoid putting probes on an int3 /breakpoint instruction ? How should it handle such situations? Below is the patch to allow probes on an int3/breakpoint instruction.
This patch fixes the above problem by doing a proper exit while avoiding recursion.
Any pointers/suggestions on the above issues will be helpful.
---
linux-2.6.12-rc1-prasanna/arch/i386/kernel/kprobes.c | 12 +++++++++++- linux-2.6.12-rc1-prasanna/arch/ppc64/kernel/kprobes.c | 12 +++++++++++- linux-2.6.12-rc1-prasanna/arch/sparc64/kernel/kprobes.c | 16 ++++++++++++++-- linux-2.6.12-rc1-prasanna/arch/x86_64/kernel/kprobes.c | 13 +++++++++++-- 4 files changed, 47 insertions(+), 6 deletions(-)
arch/i386/kernel/kprobes.c renamed from arch/i386/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -1
@@ -84,7 +84,11 @@ static inline void prepare_singlestep(st { regs->eflags |=TF_MASK ; regs->eflags &= ~IF_MASK ; - regs->eip = (unsigned long )&p->ainsn.insn; +/*single step inline if the instruction is an int3*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->eip = (unsigned long )p->addr; +else + regs->eip = (unsigned long )&p->ainsn.insn; }/*
@@ -117,6 +121,12 @@ static int kprobe_handler(struct pt_regsDisarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->eflags &= ~TF_MASK ; + regs->eflags |= kprobe_saved_eflags; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/x86_64/kernel/kprobes.c renamed from arch/x86_64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -2
@@ -108,8 +108,11 @@ static void prepare_singlestep(struct kp { regs->eflags |=TF_MASK ; regs->eflags &= ~IF_MASK ; - - regs->rip = (unsigned long )p->ainsn.insn; +/*single step inline if the instruction is an int3*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->rip = (unsigned long )p->addr; +else + regs->rip = (unsigned long )p->ainsn.insn; }/*
@@ -131,6 +134,12 @@ int kprobe_handler(struct pt_regs *regs)Disarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->eflags &= ~TF_MASK ; + regs->eflags |= kprobe_saved_rflags; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/ppc64/kernel/kprobes.c renamed from arch/ppc64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -1
@@ -71,7 +71,11 @@ static inline void disarm_kprobe(structstatic inline void prepare_singlestep (struct kprobe *p,struct pt_regs *regs) { regs->msr |=MSR_SE ; - regs->nip = (unsigned long )&p->ainsn.insn; +/*single step inline if it a breakpoint instruction*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->nip = (unsigned long )p->addr; +else + regs->nip = (unsigned long )&p->ainsn.insn; }static inline int kprobe_handler (struct pt_regs *regs)
@@ -89,6 +93,12 @@ static inline int kprobe_handler(structDisarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->msr &= ~MSR_SE ; + regs->msr |= kprobe_saved_msr; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/sparc64/kernel/kprobes.c renamed from arch/sparc64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +14 -2
@@ -68,8 +68,14 @@ static inline void prepare_singlestep(st current_kprobe_orig_tstate_pil = (regs->tstate &TSTATE_PIL ); regs->tstate |=TSTATE_PIL ; - regs->tpc = (unsigned long ) &p->ainsn.insn[0 ]; - regs->tnpc = (unsigned long ) &p->ainsn.insn[1 ]; +/*single step inline, if it a breakpoint instruction*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) { + regs->tpc = (unsigned long ) p->addr; + regs->tnpc = current_kprobe_orig_tnpc; + }else { + regs->tpc = (unsigned long ) &p->ainsn.insn[0 ]; + regs->tnpc = (unsigned long ) &p->ainsn.insn[1 ]; + } }static inline void disarm_kprobe (struct kprobe *p,struct pt_regs *regs)
@@ -97,6 +103,12 @@ static int kprobe_handler(struct pt_regs*/ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->tstate = ((regs->tstate & ~TSTATE_PIL ) | + current_kprobe_orig_tstate_pil); +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
_
Thanks
Prasanna
Signature · 5 lines
Prasanna S Panchamukhi Linux Technology Center India Software Labs, IBM Bangalore Ph: 91-80-25044636 <[email protected]>
Sorry typo error. Please use this patch.
Thanks
Prasanna
Kprobes did an improper exit when a probe is inserted on an int3 instruction. In case of normal execution of int3/breakpoint instruction, it oops!. Probe on an int3 instruction was not handled properly by the kprobes, it generated faults after oops! doing an improper exit with holding the lock. This fix employes a bit different method to handle probe on an int3/breakpoint instruction.
On execution of an int3/breakpoint instruction (placed by kprobe), kprobes_handler() is called which sets it for single stepping in-line(it does not matter whether we single step out-of-line/inline since the single stepping instruction is same). Now it single steps on int3/breakpoint instruction here, entering kprobes_handler() once again. Kprobes now check's the status that it is single stepping and avoids the recursion. It runs down through the trap handler and oops messages is seen on the console since it executed int3/breakpoint instruction. Here the kprobes single stepping handler never gets called.
Is this behaviour acceptable ? Or should we avoid putting probes on an int3 /breakpoint instruction ? How should it handle such situations? Below is the patch to allow probes on an int3/breakpoint instruction.
This patch fixes the above problem by doing a proper exit while avoiding recursion.
Any pointers/suggestions on the above issues will be helpful.
---
linux-2.6.12-rc1-prasanna/arch/i386/kernel/kprobes.c | 12 +++++++++++- linux-2.6.12-rc1-prasanna/arch/ppc64/kernel/kprobes.c | 12 +++++++++++- linux-2.6.12-rc1-prasanna/arch/sparc64/kernel/kprobes.c | 16 ++++++++++++++-- linux-2.6.12-rc1-prasanna/arch/x86_64/kernel/kprobes.c | 13 +++++++++++-- 4 files changed, 47 insertions(+), 6 deletions(-)
arch/i386/kernel/kprobes.c renamed from arch/i386/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -1
@@ -84,7 +84,11 @@ static inline void prepare_singlestep(st { regs->eflags |=TF_MASK ; regs->eflags &= ~IF_MASK ; - regs->eip = (unsigned long )&p->ainsn.insn; +/*single step inline if the instruction is an int3*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->eip = (unsigned long )p->addr; +else + regs->eip = (unsigned long )&p->ainsn.insn; }/*
@@ -117,6 +121,12 @@ static int kprobe_handler(struct pt_regsDisarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->eflags &= ~TF_MASK ; + regs->eflags |= kprobe_saved_eflags; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/x86_64/kernel/kprobes.c renamed from arch/x86_64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -2
@@ -108,8 +108,11 @@ static void prepare_singlestep(struct kp { regs->eflags |=TF_MASK ; regs->eflags &= ~IF_MASK ; - - regs->rip = (unsigned long )p->ainsn.insn; +/*single step inline if the instruction is an int3*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->rip = (unsigned long )p->addr; +else + regs->rip = (unsigned long )p->ainsn.insn; }/*
@@ -131,6 +134,12 @@ int kprobe_handler(struct pt_regs *regs)Disarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->eflags &= ~TF_MASK ; + regs->eflags |= kprobe_saved_rflags; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/ppc64/kernel/kprobes.c renamed from arch/ppc64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +11 -1
@@ -71,7 +71,11 @@ static inline void disarm_kprobe(structstatic inline void prepare_singlestep (struct kprobe *p,struct pt_regs *regs) { regs->msr |=MSR_SE ; - regs->nip = (unsigned long )&p->ainsn.insn; +/*single step inline if it a breakpoint instruction*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) + regs->nip = (unsigned long )p->addr; +else + regs->nip = (unsigned long )&p->ainsn.insn; }static inline int kprobe_handler (struct pt_regs *regs)
@@ -89,6 +93,12 @@ static inline int kprobe_handler(structDisarm the probe we just hit, and ignore it. */ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->msr &= ~MSR_SE ; + regs->msr |= kprobe_saved_msr; +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
arch/sparc64/kernel/kprobes.c renamed from arch/sparc64/kernel/kprobes.c~kprobes-allow-probes-on-int3 +14 -2
@@ -68,8 +68,14 @@ static inline void prepare_singlestep(st current_kprobe_orig_tstate_pil = (regs->tstate &TSTATE_PIL ); regs->tstate |=TSTATE_PIL ; - regs->tpc = (unsigned long ) &p->ainsn.insn[0 ]; - regs->tnpc = (unsigned long ) &p->ainsn.insn[1 ]; +/*single step inline, if it a breakpoint instruction*/ +if (p->opcode ==BREAKPOINT_INSTRUCTION ) { + regs->tpc = (unsigned long ) p->addr; + regs->tnpc = current_kprobe_orig_tnpc; + }else { + regs->tpc = (unsigned long ) &p->ainsn.insn[0 ]; + regs->tnpc = (unsigned long ) &p->ainsn.insn[1 ]; + } }static inline void disarm_kprobe (struct kprobe *p,struct pt_regs *regs)
@@ -97,6 +103,12 @@ static int kprobe_handler(struct pt_regs*/ p =get_kprobe (addr);if (p) { +if (kprobe_status ==KPROBE_HIT_SS ) { + regs->tstate = ((regs->tstate & ~TSTATE_PIL ) | + current_kprobe_orig_tstate_pil); +unlock_kprobes (); + goto no_kprobe; + }disarm_kprobe (p, regs); ret =1 ; }else {
_
Signature · 8 lines
Have a Nice Day! Thanks & Regards Prasanna S Panchamukhi Linux Technology Center India Software Labs, IBM Bangalore Ph: 91-80-25044636 <[email protected]>
Quoted 3 lines
This patch fixes the above problem by doing a proper exit while avoiding recursion.
Any pointers/suggestions on the above issues will be helpful.
Patch is fine for x86-64.
-Andi