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,
yonghong.song@linux.dev, memxor@gmail.com, awerner32@gmail.com
Subject: Re: [PATCH bpf v4 00/11] verify callbacks as if they are called unknown number of times
Date: Tue, 21 Nov 2023 03:10:25 +0000 [thread overview]
Message-ID: <170053622568.18568.10821625949332133695.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231121020701.26440-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 21 Nov 2023 04:06:50 +0200 you wrote:
> This series updates verifier logic for callback functions handling.
> Current master simulates callback body execution exactly once,
> which leads to verifier not detecting unsafe programs like below:
>
> static int unsafe_on_zero_iter_cb(__u32 idx, struct num_context *ctx)
> {
> ctx->i = 0;
> return 0;
> }
>
> [...]
Here is the summary with links:
- [bpf,v4,01/11] selftests/bpf: track tcp payload offset as scalar in xdp_synproxy
https://git.kernel.org/bpf/bpf/c/977bc146d4eb
- [bpf,v4,02/11] selftests/bpf: track string payload offset as scalar in strobemeta
https://git.kernel.org/bpf/bpf/c/87eb0152bcc1
- [bpf,v4,03/11] selftests/bpf: fix bpf_loop_bench for new callback verification scheme
https://git.kernel.org/bpf/bpf/c/f40bfd167944
- [bpf,v4,04/11] bpf: extract __check_reg_arg() utility function
https://git.kernel.org/bpf/bpf/c/683b96f9606a
- [bpf,v4,05/11] bpf: extract setup_func_entry() utility function
https://git.kernel.org/bpf/bpf/c/58124a98cb8e
- [bpf,v4,06/11] bpf: verify callbacks as if they are called unknown number of times
https://git.kernel.org/bpf/bpf/c/ab5cfac139ab
- [bpf,v4,07/11] selftests/bpf: tests for iterating callbacks
https://git.kernel.org/bpf/bpf/c/958465e217db
- [bpf,v4,08/11] bpf: widening for callback iterators
https://git.kernel.org/bpf/bpf/c/cafe2c21508a
- [bpf,v4,09/11] selftests/bpf: test widening for iterating callbacks
https://git.kernel.org/bpf/bpf/c/9f3330aa644d
- [bpf,v4,10/11] bpf: keep track of max number of bpf_loop callback iterations
https://git.kernel.org/bpf/bpf/c/bb124da69c47
- [bpf,v4,11/11] selftests/bpf: check if max number of bpf_loop iterations is tracked
https://git.kernel.org/bpf/bpf/c/57e2a52deeb1
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-11-21 3:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 2:06 [PATCH bpf v4 00/11] verify callbacks as if they are called unknown number of times Eduard Zingerman
2023-11-21 2:06 ` [PATCH bpf v4 01/11] selftests/bpf: track tcp payload offset as scalar in xdp_synproxy Eduard Zingerman
2023-11-21 2:06 ` [PATCH bpf v4 02/11] selftests/bpf: track string payload offset as scalar in strobemeta Eduard Zingerman
2023-11-21 2:06 ` [PATCH bpf v4 03/11] selftests/bpf: fix bpf_loop_bench for new callback verification scheme Eduard Zingerman
2023-11-21 2:06 ` [PATCH bpf v4 04/11] bpf: extract __check_reg_arg() utility function Eduard Zingerman
2023-11-21 2:06 ` [PATCH bpf v4 05/11] bpf: extract setup_func_entry() " Eduard Zingerman
2023-11-21 2:06 ` [PATCH bpf v4 06/11] bpf: verify callbacks as if they are called unknown number of times Eduard Zingerman
2023-11-21 3:01 ` Alexei Starovoitov
2023-11-21 2:06 ` [PATCH bpf v4 07/11] selftests/bpf: tests for iterating callbacks Eduard Zingerman
2023-11-21 2:06 ` [PATCH bpf v4 08/11] bpf: widening for callback iterators Eduard Zingerman
2023-11-21 2:06 ` [PATCH bpf v4 09/11] selftests/bpf: test widening for iterating callbacks Eduard Zingerman
2023-11-21 2:07 ` [PATCH bpf v4 10/11] bpf: keep track of max number of bpf_loop callback iterations Eduard Zingerman
2023-11-21 2:07 ` [PATCH bpf v4 11/11] selftests/bpf: check if max number of bpf_loop iterations is tracked Eduard Zingerman
2023-11-21 3:10 ` 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=170053622568.18568.10821625949332133695.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=awerner32@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=yonghong.song@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.