BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadfed@meta.com>
Cc: vadim.fedorenko@linux.dev, martin.lau@linux.dev,
	andrii@kernel.org, eddyz87@gmail.com, bpf@vger.kernel.org,
	ast@kernel.org, mykolal@fb.com, daniel@iogearbox.net
Subject: Re: [PATCH RESEND bpf-next v3 0/5] bpf: make trusted args nullable
Date: Thu, 13 Jun 2024 23:40:31 +0000	[thread overview]
Message-ID: <171832203134.25229.4899596896330603390.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240613211817.1551967-1-vadfed@meta.com>

Hello:

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

On Thu, 13 Jun 2024 14:18:12 -0700 you wrote:
> Current verifier checks for the arg to be nullable after checking for
> certain pointer types. It prevents programs to pass NULL to kfunc args
> even if they are marked as nullable. This patchset adjusts verifier and
> changes bpf crypto kfuncs to allow null for IV parameter which is
> optional for some ciphers. Benchmark shows ~4% improvements when there
> is no need to initialise 0-sized dynptr.
> 
> [...]

Here is the summary with links:
  - [RESEND,bpf-next,v3,1/5] bpf: verifier: make kfuncs args nullalble
    https://git.kernel.org/bpf/bpf-next/c/a90797993afc
  - [RESEND,bpf-next,v3,2/5] bpf: crypto: make state and IV dynptr nullable
    https://git.kernel.org/bpf/bpf-next/c/65d6d61d2596
  - [RESEND,bpf-next,v3,3/5] selftests: bpf: crypto: use NULL instead of 0-sized dynptr
    https://git.kernel.org/bpf/bpf-next/c/9363dc8ddc4e
  - [RESEND,bpf-next,v3,4/5] selftests: bpf: crypto: adjust bench to use nullable IV
    https://git.kernel.org/bpf/bpf-next/c/9b560751f75f
  - [RESEND,bpf-next,v3,5/5] selftests: bpf: add testmod kfunc for nullable params
    https://git.kernel.org/bpf/bpf-next/c/2d45ab1eda46

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-06-13 23:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 21:18 [PATCH RESEND bpf-next v3 0/5] bpf: make trusted args nullable Vadim Fedorenko
2024-06-13 21:18 ` [PATCH RESEND bpf-next v3 1/5] bpf: verifier: make kfuncs args nullalble Vadim Fedorenko
2024-06-13 21:18 ` [PATCH RESEND bpf-next v3 2/5] bpf: crypto: make state and IV dynptr nullable Vadim Fedorenko
2024-06-13 21:18 ` [PATCH RESEND bpf-next v3 3/5] selftests: bpf: crypto: use NULL instead of 0-sized dynptr Vadim Fedorenko
2024-06-13 21:18 ` [PATCH RESEND bpf-next v3 4/5] selftests: bpf: crypto: adjust bench to use nullable IV Vadim Fedorenko
2024-06-13 21:18 ` [PATCH RESEND bpf-next v3 5/5] selftests: bpf: add testmod kfunc for nullable params Vadim Fedorenko
2024-06-13 23:40 ` 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=171832203134.25229.4899596896330603390.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=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=vadfed@meta.com \
    --cc=vadim.fedorenko@linux.dev \
    /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