BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	songliubraving@fb.com, yhs@fb.com, oleg@redhat.com,
	mhiramat@kernel.org
Subject: Re: [PATCHv3 bpf-next 0/7] bpf: Allow uprobe_multi binary specified by file descriptor
Date: Mon, 15 Jun 2026 00:30:23 +0000	[thread overview]
Message-ID: <178148342339.2360960.8113242983343926626.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260611114230.950379-1-jolsa@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 11 Jun 2026 13:42:23 +0200 you wrote:
> hi,
> we'd like to be able to open uprobe_multi link on top of binary identified
> by file descriptor. This allows us to avoid the race where the binary is
> replaced between path resolution and attachment, ensuring we monitor the
> intended binary.
> 
> v1: https://lore.kernel.org/bpf/20260609104244.588321-1-jolsa@kernel.org/T/#m0275d5f39805c57dc8fd3308c640237dc7aec4db
> v2: https://lore.kernel.org/bpf/20260610143627.804790-1-jolsa@kernel.org/T/#m153e18fa426140fdcc773cc97b10e006531656c0
> 
> [...]

Here is the summary with links:
  - [PATCHv3,bpf-next,1/7] bpf: Guard __get_user acesss with access_ok for uprobe_multi data
    https://git.kernel.org/bpf/bpf-next/c/4d87a251d45b
  - [PATCHv3,bpf-next,2/7] bpf: Use user_path_at for path resolution in uprobe_multi
    https://git.kernel.org/bpf/bpf-next/c/65d81609e931
  - [PATCHv3,bpf-next,3/7] bpf: Add support to specify uprobe_multi target via file descriptor
    https://git.kernel.org/bpf/bpf-next/c/26330a922641
  - [PATCHv3,bpf-next,4/7] libbpf: Add path_fd to struct bpf_link_create_opts
    https://git.kernel.org/bpf/bpf-next/c/da3a4c3ec7ed
  - [PATCHv3,bpf-next,5/7] selftests/bpf: Add uprobe_multi path_fd test
    https://git.kernel.org/bpf/bpf-next/c/d5026e6bfc70
  - [PATCHv3,bpf-next,6/7] selftests/bpf: Add uprobe_multi path_fd fail tests
    https://git.kernel.org/bpf/bpf-next/c/3229675be841
  - [PATCHv3,bpf-next,7/7] selftests/bpf: Fix typo in verify_umulti_link_info
    https://git.kernel.org/bpf/bpf-next/c/df29003c5511

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-06-15  0:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 11:42 [PATCHv3 bpf-next 0/7] bpf: Allow uprobe_multi binary specified by file descriptor Jiri Olsa
2026-06-11 11:42 ` [PATCHv3 bpf-next 1/7] bpf: Guard __get_user acesss with access_ok for uprobe_multi data Jiri Olsa
2026-06-11 11:55   ` sashiko-bot
2026-06-15  7:58     ` Jiri Olsa
2026-06-11 11:42 ` [PATCHv3 bpf-next 2/7] bpf: Use user_path_at for path resolution in uprobe_multi Jiri Olsa
2026-06-11 11:42 ` [PATCHv3 bpf-next 3/7] bpf: Add support to specify uprobe_multi target via file descriptor Jiri Olsa
2026-06-11 11:42 ` [PATCHv3 bpf-next 4/7] libbpf: Add path_fd to struct bpf_link_create_opts Jiri Olsa
2026-06-11 11:53   ` sashiko-bot
2026-06-11 11:42 ` [PATCHv3 bpf-next 5/7] selftests/bpf: Add uprobe_multi path_fd test Jiri Olsa
2026-06-11 11:52   ` sashiko-bot
2026-06-11 11:42 ` [PATCHv3 bpf-next 6/7] selftests/bpf: Add uprobe_multi path_fd fail tests Jiri Olsa
2026-06-11 11:54   ` sashiko-bot
2026-06-11 11:42 ` [PATCHv3 bpf-next 7/7] selftests/bpf: Fix typo in verify_umulti_link_info Jiri Olsa
2026-06-15  0:30 ` patchwork-bot+netdevbpf [this message]

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=178148342339.2360960.8113242983343926626.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mhiramat@kernel.org \
    --cc=oleg@redhat.com \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    /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