From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: hongao <hongao@uniontech.com>
Cc: naveen@kernel.org, anil.s.keshavamurthy@intel.com,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] kprobes: retry pending optprobe after freeing blocker
Date: Wed, 29 Oct 2025 13:02:47 +0900 [thread overview]
Message-ID: <20251029130247.fa760b2f35f01a91c9e80eee@kernel.org> (raw)
In-Reply-To: <2B0BC73E9D190B7B+20251027130535.2296913-1-hongao@uniontech.com>
On Mon, 27 Oct 2025 21:05:35 +0800
hongao <hongao@uniontech.com> wrote:
> The freeing_list cleanup now retries optimizing any sibling probe that was
> deferred while this aggregator was being torn down. Track the pending
> address in struct optimized_kprobe so __disarm_kprobe() can defer the
> retry until kprobe_optimizer() finishes disarming.
Thanks Hongao! I have some comment below.
Please make it simpler.
>
> Signed-off-by: hongao <hongao@uniontech.com>
>
> diff --git a/include/linux/kprobes.h b/include/linux/kprobes.h
> index 8c4f3bb24..33d65b008 100644
> --- a/include/linux/kprobes.h
> +++ b/include/linux/kprobes.h
> @@ -338,6 +338,7 @@ DEFINE_INSN_CACHE_OPS(insn);
> struct optimized_kprobe {
> struct kprobe kp;
> struct list_head list; /* list for optimizing queue */
> + kprobe_opcode_t *pending_reopt_addr; /* addr that should trigger re-optimization */
You may need "bool reopt_unblocked_probes".
> struct arch_optimized_insn optinsn;
> };
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index da59c68df..0976ab57d 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -514,6 +514,7 @@ static LIST_HEAD(freeing_list);
>
> static void kprobe_optimizer(struct work_struct *work);
> static DECLARE_DELAYED_WORK(optimizing_work, kprobe_optimizer);
> +static void optimize_kprobe(struct kprobe *p);
> #define OPTIMIZE_DELAY 5
>
> /*
> @@ -591,6 +592,20 @@ static void do_free_cleaned_kprobes(void)
> */
> continue;
> }
> + if (op->pending_reopt_addr) {
> + struct kprobe *blocked;
unblocked?
> +
> + /*
> + * The aggregator was holding back another probe while it sat on the
> + * unoptimizing/freeing lists. Now that the aggregator has been fully
> + * reverted we can safely retry the optimization of that sibling.
> + */
> +
> + blocked = get_optimized_kprobe(op->pending_reopt_addr);
You can use op->kp.addr.
> + if (unlikely(blocked))
> + optimize_kprobe(blocked);
> + }
> +
> free_aggr_kprobe(&op->kp);
> }
> }
> @@ -1009,13 +1024,13 @@ static void __disarm_kprobe(struct kprobe *p, bool reopt)
> _p = get_optimized_kprobe(p->addr);
> if (unlikely(_p) && reopt)
> optimize_kprobe(_p);
> + } else if (reopt && kprobe_aggrprobe(p)) {
Here, the @p is queued. This means @p is an optprobe (and aggrprobe).
> + struct optimized_kprobe *op =
> + container_of(p, struct optimized_kprobe, kp);
> +
> + /* Defer the re-optimization until the worker finishes disarming. */
> + op->pending_reopt_addr = p->addr;
You should save the @reopt flag instead of addr.
Thank you,
> }
> - /*
> - * TODO: Since unoptimization and real disarming will be done by
> - * the worker thread, we can not check whether another probe are
> - * unoptimized because of this probe here. It should be re-optimized
> - * by the worker thread.
> - */
> }
>
> #else /* !CONFIG_OPTPROBES */
> --
> 2.47.2
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-10-29 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 13:05 [PATCH] kprobes: retry pending optprobe after freeing blocker hongao
2025-10-29 4:02 ` Masami Hiramatsu [this message]
2025-10-30 9:36 ` [[PATCH v2] 1/1] " hongao
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=20251029130247.fa760b2f35f01a91c9e80eee@kernel.org \
--to=mhiramat@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=hongao@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=naveen@kernel.org \
/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