On Mon, 24 Feb 2020 11:43:46 +0100
Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
> -dotraplinkage void notrace do_int3(struct pt_regs *regs, long error_code)
> +dotraplinkage notrace void do_int3(struct pt_regs *regs, long error_code)
> {
> if (poke_int3_handler(regs))
> return;
>
> /*
> - * Use ist_enter despite the fact that we don't use an IST stack.
> - * We can be called from a kprobe in non-CONTEXT_KERNEL kernel
> - * mode or even during context tracking state changes.
> - *
> - * This means that we can't schedule. That's okay.
> + * Unlike any other non-IST entry, we can be called from pretty much
> + * any location in the kernel through kprobes -- text_poke() will most
> + * likely be handled by poke_int3_handler() above. This means this
> + * handler is effectively NMI-like.
> */
> - ist_enter(regs);
> + nmi_enter();
Hmm, note that nmi_enter() calls other functions. Did you make sure
all of them are not able to be kprobed. This is different than just
being "NMI like", it's that if they are kprobed, then this will go into
an infinite loop because nothing can have a kprobe before the kprobe
int3 handler is called here.
-- Steve
> RCU_LOCKDEP_WARN(!rcu_is_watching(), "entry code didn't wake RCU");
> #ifdef CONFIG_KGDB_LOW_LEVEL_TRAP
> if (kgdb_ll_trap(DIE_INT3, "int3", regs, error_code, X86_TRAP_BP,
> @@ -563,7 +530,7 @@ dotraplinkage void notrace do_int3(struc
> cond_local_irq_disable(regs);
>
> exit:
> - ist_exit(regs);
> + nmi_exit();
> }
> NOKPROBE_SYMBOL(do_int3);
