Linux Trace Kernel
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jiri Olsa" <jolsa@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH 13/13] samples/kprobes: Add batch probe example
Date: Wed, 11 Nov 2026 00:49:19 +0000	[thread overview]
Message-ID: <sashiko-outbox-208036@kernel.org> (raw)
In-Reply-To: <20261109195827.1091410-1-jolsa@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] samples/kprobes: missing ANNOTATE_NOCFI_SYM() on
  kprobe_many_call_function()
--

commit 0bb6f0bd88ba358a50c5bd0da72b9a9137c6b243
Author: Jiri Olsa <jolsa@kernel.org>

samples/kprobes: Add batch probe example

This commit adds 50,000 generated x86 functions and a sample module that
registers kprobes on them in a batch and calls each function to verify
the probes.

> diff --git a/samples/kprobes/kprobe_many_example.c b/samples/kprobes/kprobe_many_example.c
> new file mode 100644
> index 0000000000000..5a58908c840c7
> --- /dev/null
> +++ b/samples/kprobes/kprobe_many_example.c

[ ... ]

> +/* The generated assembly functions have no CFI type metadata. */
> +static noinline __nocfi void
> +kprobe_many_call_function(char *functions, unsigned int index)
> +{
> +	void (*function)(void);
> +
> +	function = (void (*)(void))(functions + index * KPROBE_MANY_FUNC_SIZE);
> +	function();
> +}

[Severity: Low]
Does kprobe_many_call_function() need
ANNOTATE_NOCFI_SYM(kprobe_many_call_function)?

Because __nocfi omits the kCFI ud2 sequence before the indirect call,
building with CONFIG_MITIGATION_RETPOLINE=y, CONFIG_CALL_PADDING=y and
CONFIG_CFI=y causes objtool's validate_retpoline() to emit a "no-cfi
indirect call!" warning (breaking the build when CONFIG_OBJTOOL_WERROR=y
is enabled) unless the function symbol is annotated with
ANNOTATE_NOCFI_SYM().

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261109194916.1089703-1-jolsa@kernel.org?part=13

  reply	other threads:[~2026-11-11  0:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 19:49 [PATCH 00/13] kprobes: Reduce registration and optimization lookup costs Jiri Olsa
2026-11-09 19:49 ` [PATCH 01/13] static_call: Index code text reservation lookups Jiri Olsa
2026-11-09 19:49 ` [PATCH 02/13] jump_label: Index " Jiri Olsa
2026-11-09 19:49 ` [PATCH 03/13] jump_label/x86: Avoid decoding instructions for jump entry size Jiri Olsa
2026-11-09 19:55 ` [PATCH 04/13] kprobes: Maintain an rbtree of registered probes Jiri Olsa
2026-11-10  8:12   ` Masami Hiramatsu (Google)
2026-11-10 10:37     ` Jiri Olsa
2026-11-10 15:38       ` Masami Hiramatsu (Google)
2026-11-11 10:49         ` Jiri Olsa
2026-11-10 23:45   ` sashiko-bot
2026-11-09 19:56 ` [PATCH 05/13] kprobes: Add an iterator for address ranges Jiri Olsa
2026-11-09 19:56 ` [PATCH 06/13] kprobes: Add an address iterator for probe lookup Jiri Olsa
2026-11-09 19:56 ` [PATCH 07/13] kprobes: Use kprobe iterator in get_optimized_kprobe Jiri Olsa
2026-11-09 19:57 ` [PATCH 08/13] x86/kprobes: Use kprobe iterator in __recover_optprobed_insn Jiri Olsa
2026-11-09 19:57 ` [PATCH 09/13] x86/kprobes: Use kprobe iterator in arch_check_optimized_kprobe Jiri Olsa
2026-11-11  0:17   ` sashiko-bot
2026-11-09 19:57 ` [PATCH 10/13] x86/kprobes: Use kprobe address iterator in can_optimize Jiri Olsa
2026-11-09 19:57 ` [PATCH 11/13] x86/kprobes: Use kprobe address iterator in can_probe Jiri Olsa
2026-11-09 19:58 ` [PATCH 12/13] x86/kprobes: Use kprobe address iterator in in copy_optimized_instructions Jiri Olsa
2026-11-09 19:58 ` [PATCH 13/13] samples/kprobes: Add batch probe example Jiri Olsa
2026-11-11  0:49   ` sashiko-bot [this message]
2026-11-11  2:20   ` kernel test robot

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=sashiko-outbox-208036@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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