From: Cupertino Miranda <cupertino.miranda@oracle.com>
To: bpf@vger.kernel.org
Cc: Cupertino Miranda <cupertino.miranda@oracle.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
"Jose E. Marchesi" <jose.marchesi@oracle.com>
Subject: Re: [PATCH bpf-next v4 0/7] bpf/verifier: range computation improvements
Date: Fri, 03 May 2024 15:14:16 +0100 [thread overview]
Message-ID: <87ikzvt22v.fsf@oracle.com> (raw)
In-Reply-To: <20240429212250.78420-1-cupertino.miranda@oracle.com>
Hi everyone,
I wonder if there is anything else to do for this patch series.
Alexei: Without that later removed change in patch 2, the intermediate
state of the patches does not properly work. Eduard refered to that and
agreed in the review for patch 7.
Best regards,
Cupertino
Cupertino Miranda writes:
> Hi everyone,
>
> New version.
> There is one extra patch which implements some code improvements
> suggested by Andrii.
>
> Thanks for your reviews!
>
> Regards,
> Cupertino
>
> Changes from v1:
> - Reordered patches in the series.
> - Fix refactor to be acurate with original code.
> - Fixed other mentioned small problems.
>
> Changes from v2:
> - Added a patch to replace mark_reg_unknowon for __mark_reg_unknown in
> the context of range computation.
> - Reverted implementation of refactor to v1 which used a simpler
> boolean return value in check function.
> - Further relaxed MUL to allow it to still compute a range when neither
> of its registers is a known value.
> - Simplified tests based on Eduards example.
> - Added messages in selftest commits.
>
> Changes from v3:
> - Improved commit message of patch nr 1.
> - Coding style fixes.
> - Improve XOR and OR tests.
> - Made function calls to pass struct bpf_reg_state pointer instead.
> - Improved final code as a last patch.
>
> Cupertino Miranda (7):
> bpf/verifier: replace calls to mark_reg_unknown.
> bpf/verifier: refactor checks for range computation
> bpf/verifier: improve XOR and OR range computation
> selftests/bpf: XOR and OR range computation tests.
> bpf/verifier: relax MUL range computation check
> selftests/bpf: MUL range computation tests.
> bpf/verifier: improve code after range computation recent changes.
>
> kernel/bpf/verifier.c | 111 ++++++++----------
> .../selftests/bpf/progs/verifier_bounds.c | 63 ++++++++++
> 2 files changed, 109 insertions(+), 65 deletions(-)
next prev parent reply other threads:[~2024-05-03 14:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 21:22 [PATCH bpf-next v4 0/7] bpf/verifier: range computation improvements Cupertino Miranda
2024-04-29 21:22 ` [PATCH bpf-next v4 1/7] bpf/verifier: replace calls to mark_reg_unknown Cupertino Miranda
2024-04-29 21:22 ` [PATCH bpf-next v4 2/7] bpf/verifier: refactor checks for range computation Cupertino Miranda
2024-04-29 23:18 ` Eduard Zingerman
2024-04-30 7:17 ` Cupertino Miranda
2024-04-30 14:52 ` Alexei Starovoitov
2024-04-29 21:22 ` [PATCH bpf-next v4 3/7] bpf/verifier: improve XOR and OR " Cupertino Miranda
2024-04-29 21:22 ` [PATCH bpf-next v4 4/7] selftests/bpf: XOR and OR range computation tests Cupertino Miranda
2024-04-29 21:22 ` [PATCH bpf-next v4 5/7] bpf/verifier: relax MUL range computation check Cupertino Miranda
2024-04-29 21:22 ` [PATCH bpf-next v4 6/7] selftests/bpf: MUL range computation tests Cupertino Miranda
2024-04-29 21:22 ` [PATCH bpf-next v4 7/7] bpf/verifier: improve code after range computation recent changes Cupertino Miranda
2024-04-29 23:16 ` Eduard Zingerman
2024-04-29 23:29 ` Eduard Zingerman
2024-04-30 16:48 ` Eduard Zingerman
2024-05-03 14:14 ` Cupertino Miranda [this message]
2024-05-03 16:20 ` [PATCH bpf-next v4 0/7] bpf/verifier: range computation improvements Alexei Starovoitov
2024-05-03 16:42 ` Cupertino Miranda
2024-05-03 18:18 ` Eduard Zingerman
2024-05-03 19:33 ` Cupertino Miranda
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=87ikzvt22v.fsf@oracle.com \
--to=cupertino.miranda@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=jose.marchesi@oracle.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;
as well as URLs for NNTP newsgroup(s).