All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Anton Protopopov <aspsk@isovalent.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v5 bpf-next 0/7] Add fd_array_cnt attribute for BPF_PROG_LOAD
Date: Fri, 13 Dec 2024 23:10:32 +0000	[thread overview]
Message-ID: <173413143251.3187520.18077942591138065487.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241213130934.1087929-1-aspsk@isovalent.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Fri, 13 Dec 2024 13:09:27 +0000 you wrote:
> Add a new attribute to the bpf(BPF_PROG_LOAD) system call. If this
> new attribute is non-zero, then the fd_array is considered to be a
> continuous array of the fd_array_cnt length and to contain only
> proper map file descriptors or btf file descriptors.
> 
> This change allows maps (and btfs), which aren't referenced directly
> by a BPF program, to be bound to the program _and_ also to be present
> during the program verification (so BPF_PROG_BIND_MAP is not enough
> for this use case).
> 
> [...]

Here is the summary with links:
  - [v5,bpf-next,1/7] bpf: add a __btf_get_by_fd helper
    https://git.kernel.org/bpf/bpf-next/c/4e885fab7164
  - [v5,bpf-next,2/7] bpf: move map/prog compatibility checks
    https://git.kernel.org/bpf/bpf-next/c/928f3221cb14
  - [v5,bpf-next,3/7] bpf: refactor check_pseudo_btf_id
    https://git.kernel.org/bpf/bpf-next/c/76145f725532
  - [v5,bpf-next,4/7] bpf: add fd_array_cnt attribute for prog_load
    https://git.kernel.org/bpf/bpf-next/c/4d3ae294f900
  - [v5,bpf-next,5/7] libbpf: prog load: allow to use fd_array_cnt
    https://git.kernel.org/bpf/bpf-next/c/f9933acda31a
  - [v5,bpf-next,6/7] selftests/bpf: Add tests for fd_array_cnt
    https://git.kernel.org/bpf/bpf-next/c/1c593d7402b1
  - [v5,bpf-next,7/7] selftest/bpf: replace magic constants by macros
    https://git.kernel.org/bpf/bpf-next/c/d677a10f80ab

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



      parent reply	other threads:[~2024-12-13 23:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 13:09 [PATCH v5 bpf-next 0/7] Add fd_array_cnt attribute for BPF_PROG_LOAD Anton Protopopov
2024-12-13 13:09 ` [PATCH v5 bpf-next 1/7] bpf: add a __btf_get_by_fd helper Anton Protopopov
2024-12-13 13:09 ` [PATCH v5 bpf-next 2/7] bpf: move map/prog compatibility checks Anton Protopopov
2024-12-13 13:09 ` [PATCH v5 bpf-next 3/7] bpf: refactor check_pseudo_btf_id Anton Protopopov
2024-12-13 22:17   ` Andrii Nakryiko
2024-12-13 13:09 ` [PATCH v5 bpf-next 4/7] bpf: add fd_array_cnt attribute for prog_load Anton Protopopov
2024-12-13 22:18   ` Andrii Nakryiko
2024-12-14  5:12     ` Anton Protopopov
2024-12-13 13:09 ` [PATCH v5 bpf-next 5/7] libbpf: prog load: allow to use fd_array_cnt Anton Protopopov
2024-12-13 13:09 ` [PATCH v5 bpf-next 6/7] selftests/bpf: Add tests for fd_array_cnt Anton Protopopov
2024-12-13 13:09 ` [PATCH v5 bpf-next 7/7] selftest/bpf: replace magic constants by macros Anton Protopopov
2024-12-13 23:10 ` 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=173413143251.3187520.18077942591138065487.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aspsk@isovalent.com \
    --cc=bpf@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.