From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yhs@fb.com
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Allow reads from uninit stack
Date: Wed, 22 Feb 2023 20:50:16 +0000 [thread overview]
Message-ID: <167709901684.29904.12690598164971386254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230219200427.606541-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 19 Feb 2023 22:04:25 +0200 you wrote:
> This patch-set modifies BPF verifier to accept programs that read from
> uninitialized stack locations, but only if executed in privileged mode.
> This provides significant verification performance gains: 30% to 70% less
> processed states for big number of test programs.
>
> The reason for performance gains comes from treating STACK_MISC and
> STACK_INVALID as compatible, when cached state is compared to current state
> in verifier.c:stacksafe().
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Allow reads from uninit stack
https://git.kernel.org/bpf/bpf-next/c/6715df8d5d24
- [bpf-next,v2,2/2] selftests/bpf: Tests for uninitialized stack reads
https://git.kernel.org/bpf/bpf-next/c/6338a94d5ab4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-22 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 20:04 [PATCH bpf-next v2 0/2] bpf: Allow reads from uninit stack Eduard Zingerman
2023-02-19 20:04 ` [PATCH bpf-next v2 1/2] " Eduard Zingerman
2023-02-19 20:04 ` [PATCH bpf-next v2 2/2] selftests/bpf: Tests for uninitialized stack reads Eduard Zingerman
2023-02-22 20: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=167709901684.29904.12690598164971386254.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=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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