public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, joannelkoong@gmail.com, toke@redhat.com,
	brouer@redhat.com
Subject: Re: [PATCH bpf-next v6 00/13] Introduce typed pointer support in BPF maps
Date: Tue, 26 Apr 2022 03:30:13 +0000	[thread overview]
Message-ID: <165094381372.16200.4266574915609138516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220424214901.2743946-1-memxor@gmail.com>

Hello:

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

On Mon, 25 Apr 2022 03:18:48 +0530 you wrote:
> This set enables storing pointers of a certain type in BPF map, and extends the
> verifier to enforce type safety and lifetime correctness properties.
> 
> The infrastructure being added is generic enough for allowing storing any kind
> of pointers whose type is available using BTF (user or kernel) in the future
> (e.g. strongly typed memory allocation in BPF program), which are internally
> tracked in the verifier as PTR_TO_BTF_ID, but for now the series limits them to
> two kinds of pointers obtained from the kernel.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,01/13] bpf: Allow storing unreferenced kptr in map
    https://git.kernel.org/bpf/bpf-next/c/61df10c7799e
  - [bpf-next,v6,02/13] bpf: Tag argument to be released in bpf_func_proto
    https://git.kernel.org/bpf/bpf-next/c/8f14852e8911
  - [bpf-next,v6,03/13] bpf: Allow storing referenced kptr in map
    https://git.kernel.org/bpf/bpf-next/c/c0a5a21c25f3
  - [bpf-next,v6,04/13] bpf: Prevent escaping of kptr loaded from maps
    https://git.kernel.org/bpf/bpf-next/c/6efe152d4061
  - [bpf-next,v6,05/13] bpf: Adapt copy_map_value for multiple offset case
    https://git.kernel.org/bpf/bpf-next/c/4d7d7f69f4b1
  - [bpf-next,v6,06/13] bpf: Populate pairs of btf_id and destructor kfunc in btf
    https://git.kernel.org/bpf/bpf-next/c/5ce937d613a4
  - [bpf-next,v6,07/13] bpf: Wire up freeing of referenced kptr
    https://git.kernel.org/bpf/bpf-next/c/14a324f6a67e
  - [bpf-next,v6,08/13] bpf: Teach verifier about kptr_get kfunc helpers
    https://git.kernel.org/bpf/bpf-next/c/a1ef19599652
  - [bpf-next,v6,09/13] bpf: Make BTF type match stricter for release arguments
    https://git.kernel.org/bpf/bpf-next/c/2ab3b3808eb1
  - [bpf-next,v6,10/13] libbpf: Add kptr type tag macros to bpf_helpers.h
    https://git.kernel.org/bpf/bpf-next/c/ef89654f2bc7
  - [bpf-next,v6,11/13] selftests/bpf: Add C tests for kptr
    https://git.kernel.org/bpf/bpf-next/c/2cbc469a6fc3
  - [bpf-next,v6,12/13] selftests/bpf: Add verifier tests for kptr
    https://git.kernel.org/bpf/bpf-next/c/05a945deefaa
  - [bpf-next,v6,13/13] selftests/bpf: Add test for strict BTF type check
    https://git.kernel.org/bpf/bpf-next/c/792c0a345f0e

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



      parent reply	other threads:[~2022-04-26  3:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 21:48 [PATCH bpf-next v6 00/13] Introduce typed pointer support in BPF maps Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 01/13] bpf: Allow storing unreferenced kptr in map Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 02/13] bpf: Tag argument to be released in bpf_func_proto Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 03/13] bpf: Allow storing referenced kptr in map Kumar Kartikeya Dwivedi
2022-04-26  3:30   ` Alexei Starovoitov
2022-04-24 21:48 ` [PATCH bpf-next v6 04/13] bpf: Prevent escaping of kptr loaded from maps Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 05/13] bpf: Adapt copy_map_value for multiple offset case Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 06/13] bpf: Populate pairs of btf_id and destructor kfunc in btf Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 07/13] bpf: Wire up freeing of referenced kptr Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 08/13] bpf: Teach verifier about kptr_get kfunc helpers Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 09/13] bpf: Make BTF type match stricter for release arguments Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 10/13] libbpf: Add kptr type tag macros to bpf_helpers.h Kumar Kartikeya Dwivedi
2022-04-24 21:48 ` [PATCH bpf-next v6 11/13] selftests/bpf: Add C tests for kptr Kumar Kartikeya Dwivedi
2022-04-24 21:49 ` [PATCH bpf-next v6 12/13] selftests/bpf: Add verifier " Kumar Kartikeya Dwivedi
2022-04-26  3:35   ` Alexei Starovoitov
2022-05-09 20:03     ` Kumar Kartikeya Dwivedi
2022-04-24 21:49 ` [PATCH bpf-next v6 13/13] selftests/bpf: Add test for strict BTF type check Kumar Kartikeya Dwivedi
2022-04-26  3:39   ` Alexei Starovoitov
2022-05-08 21:59     ` Alexei Starovoitov
2022-05-09 19:49       ` Kumar Kartikeya Dwivedi
2022-04-26  3: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=165094381372.16200.4266574915609138516.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=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=joannelkoong@gmail.com \
    --cc=memxor@gmail.com \
    --cc=toke@redhat.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