Re: [PATCH v1 0/4] Fix ftrace and kprobes issues for LoongArch

From: Huacai Chen

Date: Thu May 21 2026 - 08:59:55 EST


On Thu, May 21, 2026 at 10:37 AM Tiezhu Yang <yangtiezhu@xxxxxxxxxxx> wrote:
>
> On 2026/5/20 下午3:58, Huacai Chen wrote:
> > Hi, Tiezhu,
> >
> > On Fri, May 15, 2026 at 12:29 PM Huacai Chen <chenhuacai@xxxxxxxxxx> wrote:
> >>
> >> On Fri, May 15, 2026 at 10:52 AM Tiezhu Yang <yangtiezhu@xxxxxxxxxxx> wrote:
> >>>
> >>> On 2026/5/12 下午4:20, Tiezhu Yang wrote:
> >>>> This series addresses ftrace and kprobes issues observed under heavy
> >>>> tracing loads.
> >>>>
> >>>> Tiezhu Yang (4):
> >>>> LoongArch: ftrace: Fix stale per-CPU kprobe state after task migration
> >>>> LoongArch: kprobes: Use larch_insn_text_copy() to patch instructions
> >>>> LoongArch: kprobes: Fix single-stepping instruction slot preparation
> >>>> LoongArch: kprobes: Fix handling of fatal unrecoverable recursions
> >>>
> >>> Hi Lisa and Rui,
> >>>
> >>> You are right, please ignore the patch #3.
> >> I think Patch#3 is OK, but you need to remove the introduction about atomicity.
> > Will you resend V2? Or just ignore Patch#3?
>
> I think no need to send v2.
>
> Please disregard patch #1 and #3,
> I will tell you more info in the inner meeting.
>
> Please only consider patch #2 and #4.
OK, but I want to remove preempt_enable_no_resched() in Patch#4
because all other architectures have no.

Huacai

>
> Thanks,
> Tiezhu
>
>