The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lisa Robinson <lisa@bytefly.space>
To: yangtiezhu@loongson.cn
Cc: chenhuacai@kernel.org, linux-kernel@vger.kernel.org,
	loongarch@lists.linux.dev, Lisa Robinson <lisa@bytefly.space>
Subject: Re: [PATCH v1 3/4] LoongArch: kprobes: Fix single-stepping instruction slot preparation
Date: Wed, 13 May 2026 14:15:14 +0800	[thread overview]
Message-ID: <20260513061514.83-1-lisa@bytefly.space> (raw)
In-Reply-To: <20260512082029.2131-4-yangtiezhu@loongson.cn>

> In arch_prepare_ss_slot(), the original code directly assigns instructions
> to the buffer using raw memory stores. This approach has two significant
> drawbacks on LoongArch:
> 
> 1. Consistency: It skips the necessary instruction barrier synchronization
>    required by the architecture. Without a local barrier, the instruction
>    fetch unit might not observe the newly prepared instructions in the
>    single-step slot, even on the local CPU.
> 2. Atomicity: Raw memory assignments do not guarantee that the instruction
>    unit sees a complete instruction at all times, which is critical for
>    the integrity of single-step execution.
> 
> Like RISC-V and ARM64, use larch_insn_patch_text() for slot preparation to
> ensure the atomic instruction writes and proper local instruction barrier
> execution.
> 
> Note that global stop_machine synchronization is not required here because
> the single-step slot is executed only after a breakpoint exception, which
> inherently provides a context synchronization event for the CPU to observe
> the new instructions.
> 
> Fixes: 6d4cc40fb5f5 ("LoongArch: Add kprobes support")
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
>  arch/loongarch/kernel/kprobes.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/loongarch/kernel/kprobes.c b/arch/loongarch/kernel/kprobes.c
> index 04b5b05715cd..8e1b7a87c897 100644
> --- a/arch/loongarch/kernel/kprobes.c
> +++ b/arch/loongarch/kernel/kprobes.c
> @@ -12,8 +12,8 @@ DEFINE_PER_CPU(struct kprobe_ctlblk, kprobe_ctlblk);
>  
>  static void arch_prepare_ss_slot(struct kprobe *p)
>  {
> -	p->ainsn.insn[0] = *p->addr;
> -	p->ainsn.insn[1] = KPROBE_SSTEPBP_INSN;
> +	larch_insn_patch_text(p->ainsn.insn, *p->addr);
> +	larch_insn_patch_text(p->ainsn.insn + 1, KPROBE_SSTEPBP_INSN);

This instruction sequence is executed only after arch_arm_kprobe(), so any
instruction hazards are prevented.

--
Lisa

>  	p->ainsn.restore = (unsigned long)p->addr + LOONGARCH_INSN_SIZE;
>  }
>  NOKPROBE_SYMBOL(arch_prepare_ss_slot);
> -- 
> 2.42.0

  reply	other threads:[~2026-05-13  6:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  8:20 [PATCH v1 0/4] Fix ftrace and kprobes issues for LoongArch Tiezhu Yang
2026-05-12  8:20 ` [PATCH v1 1/4] LoongArch: ftrace: Fix stale per-CPU kprobe state after task migration Tiezhu Yang
2026-05-12  8:20 ` [PATCH v1 2/4] LoongArch: kprobes: Use larch_insn_text_copy() to patch instructions Tiezhu Yang
2026-05-12  8:20 ` [PATCH v1 3/4] LoongArch: kprobes: Fix single-stepping instruction slot preparation Tiezhu Yang
2026-05-13  6:15   ` Lisa Robinson [this message]
2026-05-14 13:20   ` WANG Rui
2026-05-12  8:20 ` [PATCH v1 4/4] LoongArch: kprobes: Fix handling of fatal unrecoverable recursions Tiezhu Yang
2026-05-15  2:52 ` [PATCH v1 0/4] Fix ftrace and kprobes issues for LoongArch Tiezhu Yang
2026-05-15  4:29   ` Huacai Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260513061514.83-1-lisa@bytefly.space \
    --to=lisa@bytefly.space \
    --cc=chenhuacai@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=yangtiezhu@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox