BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v5 bpf-next 00/11] BPF verifier retval logic fixes
Date: Sat, 02 Dec 2023 19:50:24 +0000	[thread overview]
Message-ID: <170154662480.24068.17331374520976496931.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231202175705.885270-1-andrii@kernel.org>

Hello:

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

On Sat, 2 Dec 2023 09:56:54 -0800 you wrote:
> This patch set fixes BPF verifier logic around validating and enforcing return
> values for BPF programs that have specific range of expected return values.
> Both sync and async callbacks have similar logic and are fixes as well.
> A few tests are added that would fail without the fixes in this patch set.
> 
> Also, while at it, we update retval checking logic to use smin/smax range
> instead of tnum, avoiding future potential issues if expected range cannot be
> represented precisely by tnum (e.g., [0, 2] is not representable by tnum and
> is treated as [0, 3]).
> 
> [...]

Here is the summary with links:
  - [v5,bpf-next,01/11] bpf: rearrange bpf_func_state fields to save a bit of memory
    https://git.kernel.org/bpf/bpf-next/c/45b5623f2d72
  - [v5,bpf-next,02/11] bpf: provide correct register name for exception callback retval check
    https://git.kernel.org/bpf/bpf-next/c/5fad52bee304
  - [v5,bpf-next,03/11] bpf: enforce precision of R0 on callback return
    https://git.kernel.org/bpf/bpf-next/c/0acd03a5bd18
  - [v5,bpf-next,04/11] bpf: enforce exact retval range on subprog/callback exit
    https://git.kernel.org/bpf/bpf-next/c/8fa4ecd49b81
  - [v5,bpf-next,05/11] selftests/bpf: add selftest validating callback result is enforced
    https://git.kernel.org/bpf/bpf-next/c/60a6b2c78c62
  - [v5,bpf-next,06/11] bpf: enforce precise retval range on program exit
    https://git.kernel.org/bpf/bpf-next/c/c871d0e00f0e
  - [v5,bpf-next,07/11] bpf: unify async callback and program retval checks
    https://git.kernel.org/bpf/bpf-next/c/0ef24c8dfae2
  - [v5,bpf-next,08/11] bpf: enforce precision of R0 on program/async callback return
    https://git.kernel.org/bpf/bpf-next/c/eabe518de533
  - [v5,bpf-next,09/11] selftests/bpf: validate async callback return value check correctness
    https://git.kernel.org/bpf/bpf-next/c/e02dea158dda
  - [v5,bpf-next,10/11] selftests/bpf: adjust global_func15 test to validate prog exit precision
    https://git.kernel.org/bpf/bpf-next/c/5c19e1d05e9e
  - [v5,bpf-next,11/11] bpf: simplify tnum output if a fully known constant
    https://git.kernel.org/bpf/bpf-next/c/81eff2e36481

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



      parent reply	other threads:[~2023-12-02 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-02 17:56 [PATCH v5 bpf-next 00/11] BPF verifier retval logic fixes Andrii Nakryiko
2023-12-02 17:56 ` [PATCH v5 bpf-next 01/11] bpf: rearrange bpf_func_state fields to save a bit of memory Andrii Nakryiko
2023-12-02 17:56 ` [PATCH v5 bpf-next 02/11] bpf: provide correct register name for exception callback retval check Andrii Nakryiko
2023-12-02 17:56 ` [PATCH v5 bpf-next 03/11] bpf: enforce precision of R0 on callback return Andrii Nakryiko
2023-12-02 17:56 ` [PATCH v5 bpf-next 04/11] bpf: enforce exact retval range on subprog/callback exit Andrii Nakryiko
2023-12-02 17:56 ` [PATCH v5 bpf-next 05/11] selftests/bpf: add selftest validating callback result is enforced Andrii Nakryiko
2023-12-02 17:57 ` [PATCH v5 bpf-next 06/11] bpf: enforce precise retval range on program exit Andrii Nakryiko
2023-12-02 17:57 ` [PATCH v5 bpf-next 07/11] bpf: unify async callback and program retval checks Andrii Nakryiko
2023-12-02 17:57 ` [PATCH v5 bpf-next 08/11] bpf: enforce precision of R0 on program/async callback return Andrii Nakryiko
2023-12-02 17:57 ` [PATCH v5 bpf-next 09/11] selftests/bpf: validate async callback return value check correctness Andrii Nakryiko
2023-12-02 17:57 ` [PATCH v5 bpf-next 10/11] selftests/bpf: adjust global_func15 test to validate prog exit precision Andrii Nakryiko
2023-12-02 17:57 ` [PATCH v5 bpf-next 11/11] bpf: simplify tnum output if a fully known constant Andrii Nakryiko
2023-12-02 19:50 ` 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=170154662480.24068.17331374520976496931.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=kernel-team@meta.com \
    --cc=martin.lau@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