BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Maxim Mikityanskiy <maximmi@nvidia.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	john.fastabend@gmail.com, kpsingh@kernel.org, shuah@kernel.org,
	davem@davemloft.net, kuba@kernel.org, hawk@kernel.org,
	bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf] bpf: Add selftests to cover packet access corner cases
Date: Wed, 08 Dec 2021 14:50:09 +0000	[thread overview]
Message-ID: <163897500902.29831.2324466346269128478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211207081521.41923-1-maximmi@nvidia.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Tue, 7 Dec 2021 10:15:21 +0200 you wrote:
> This commit adds BPF verifier selftests that cover all corner cases by
> packet boundary checks. Specifically, 8-byte packet reads are tested at
> the beginning of data and at the beginning of data_meta, using all kinds
> of boundary checks (all comparison operators: <, >, <=, >=; both
> permutations of operands: data + length compared to end, end compared to
> data + length). For each case there are three tests:
> 
> [...]

Here is the summary with links:
  - [bpf] bpf: Add selftests to cover packet access corner cases
    https://git.kernel.org/bpf/bpf/c/b560b21f71eb

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



      reply	other threads:[~2021-12-08 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  8:15 [PATCH bpf] bpf: Add selftests to cover packet access corner cases Maxim Mikityanskiy
2021-12-08 14: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=163897500902.29831.2324466346269128478.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=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=maximmi@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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