From: Huacai Chen <chenhuacai@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Lisa Robinson <lisa@bytefly.space>, WANG Rui <r@hev.cc>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] Fix ftrace and kprobes issues for LoongArch
Date: Fri, 15 May 2026 12:29:34 +0800 [thread overview]
Message-ID: <CAAhV-H7aR3NBpTk8Nbg0bphuXoDXa+xjo=bMLbrApm-SwvJYOw@mail.gmail.com> (raw)
In-Reply-To: <e7100f76-01f4-0dce-f774-045163d10f30@loongson.cn>
On Fri, May 15, 2026 at 10:52 AM Tiezhu Yang <yangtiezhu@loongson.cn> 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.
Huacai
>
> Hi Huacai,
>
> Please disregard the patch #1 and focus on the patch #2 and #4.
>
> After thinking it through, it is better to avoid calling functions that
> might sleep in the probe handler. We have modified the test module with
> a proper way, there is no problem thereafter.
>
> The right way is to prevent the problem at the root instead of trying to
> fix it after the fact.
>
> Thanks,
> Tiezhu
>
>
next prev parent reply other threads:[~2026-05-15 4:29 UTC|newest]
Thread overview: 15+ 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
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 [this message]
2026-05-20 7:58 ` Huacai Chen
2026-05-21 2:37 ` Tiezhu Yang
2026-05-21 12:52 ` Huacai Chen
2026-05-22 2:16 ` Tiezhu Yang
2026-05-22 2:40 ` Huacai Chen
2026-05-22 3:02 ` Tiezhu Yang
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='CAAhV-H7aR3NBpTk8Nbg0bphuXoDXa+xjo=bMLbrApm-SwvJYOw@mail.gmail.com' \
--to=chenhuacai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@bytefly.space \
--cc=loongarch@lists.linux.dev \
--cc=r@hev.cc \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).