From: patchwork-bot+netdevbpf@kernel.org
To: Lorenz Bauer <lmb@cloudflare.com>
Cc: shuah@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kernel-team@cloudflare.com,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] selftests: bpf: check map in map pruning
Date: Fri, 12 Nov 2021 15:20:07 +0000 [thread overview]
Message-ID: <163673040779.12963.16453161654886346779.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211111161452.86864-1-lmb@cloudflare.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 11 Nov 2021 16:14:52 +0000 you wrote:
> Ensure that two registers with a map_value loaded from a nested
> map are considered equivalent for the purpose of state pruning
> and don't cause the verifier to revisit a pruning point.
>
> This uses a rather crude match on the number of insns visited by
> the verifier, which might change in the future. I've therefore
> tried to keep the code as "unpruneable" as possible by having
> the code paths only converge on the second to last instruction.
>
> [...]
Here is the summary with links:
- [bpf] selftests: bpf: check map in map pruning
https://git.kernel.org/bpf/bpf/c/a583309d968b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-11-12 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 16:14 [PATCH bpf] selftests: bpf: check map in map pruning Lorenz Bauer
2021-11-12 15:20 ` patchwork-bot+netdevbpf [this message]
2021-11-13 1:27 ` Alexei Starovoitov
2021-11-17 8:47 ` Lorenz Bauer
2021-11-18 1:00 ` Alexei Starovoitov
2021-11-18 1:29 ` Andrii Nakryiko
2021-11-18 1:38 ` Andrii Nakryiko
2021-11-18 11:05 ` Ilya Leoshkevich
2021-11-18 11:56 ` Ilya Leoshkevich
2021-11-18 15:20 ` KP Singh
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=163673040779.12963.16453161654886346779.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@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lmb@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).