public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
	ast@kernel.org, memxor@gmail.com, daniel@iogearbox.net,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	eddyz87@gmail.com, andrii@kernel.org
Subject: Re: [PATCH bpf-next v7 0/5] Support eliding map lookup nullness
Date: Fri, 17 Jan 2025 02:10:38 +0000	[thread overview]
Message-ID: <173707983824.1659522.18019002875638405637.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1736886479.git.dxu@dxuuu.xyz>

Hello:

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

On Tue, 14 Jan 2025 13:28:41 -0700 you wrote:
> This patch allows progs to elide a null check on statically known map
> lookup keys. In other words, if the verifier can statically prove that
> the lookup will be in-bounds, allow the prog to drop the null check.
> 
> This is useful for two reasons:
> 
> 1. Large numbers of nullness checks (especially when they cannot fail)
>    unnecessarily pushes prog towards BPF_COMPLEXITY_LIMIT_JMP_SEQ.
> 2. It forms a tighter contract between programmer and verifier.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v7,1/5] bpf: verifier: Add missing newline on verbose() call
    https://git.kernel.org/bpf/bpf-next/c/b8a81b5dd645
  - [bpf-next,v7,2/5] bpf: tcp: Mark bpf_load_hdr_opt() arg2 as read-write
    https://git.kernel.org/bpf/bpf-next/c/8ac412a33611
  - [bpf-next,v7,3/5] bpf: verifier: Refactor helper access type tracking
    https://git.kernel.org/bpf/bpf-next/c/37cce22dbd51
  - [bpf-next,v7,4/5] bpf: verifier: Support eliding map lookup nullness
    https://git.kernel.org/bpf/bpf-next/c/d2102f2f5d75
  - [bpf-next,v7,5/5] bpf: selftests: verifier: Add nullness elision tests
    https://git.kernel.org/bpf/bpf-next/c/f932a8e4824b

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



      parent reply	other threads:[~2025-01-17  2:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 20:28 [PATCH bpf-next v7 0/5] Support eliding map lookup nullness Daniel Xu
2025-01-14 20:28 ` [PATCH bpf-next v7 1/5] bpf: verifier: Add missing newline on verbose() call Daniel Xu
2025-01-14 20:28 ` [PATCH bpf-next v7 2/5] bpf: tcp: Mark bpf_load_hdr_opt() arg2 as read-write Daniel Xu
2025-01-14 20:28 ` [PATCH bpf-next v7 3/5] bpf: verifier: Refactor helper access type tracking Daniel Xu
2025-01-14 20:28 ` [PATCH bpf-next v7 4/5] bpf: verifier: Support eliding map lookup nullness Daniel Xu
2025-01-29 14:58   ` Ilya Leoshkevich
2025-01-29 16:49     ` Daniel Xu
2025-01-29 17:45       ` Daniel Xu
2025-01-30 10:06         ` Ilya Leoshkevich
2025-01-30 18:41           ` Daniel Xu
2025-02-01 12:04             ` Daniel Xu
2025-01-30 10:48         ` Marc Hartmayer
2025-01-14 20:28 ` [PATCH bpf-next v7 5/5] bpf: selftests: verifier: Add nullness elision tests Daniel Xu
2025-01-17  2: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=173707983824.1659522.18019002875638405637.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=dxu@dxuuu.xyz \
    --cc=eddyz87@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=memxor@gmail.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox