From: Cupertino Miranda <cupertino.miranda@oracle.com>
To: bpf@vger.kernel.org
Cc: Cupertino Miranda <cupertino.miranda@oracle.com>,
Eduard Zingerman <eddyz87@gmail.com>
Subject: Re: [PATCH bpf-next v3 0/6] bpf/verifier: range computation improvements
Date: Wed, 24 Apr 2024 23:45:25 +0100 [thread overview]
Message-ID: <87mspi8jne.fsf@oracle.com> (raw)
In-Reply-To: <20240424224053.471771-1-cupertino.miranda@oracle.com>
+Cc: Eduard Zingerman <eddyz87@gmail.com>
Apologies Eduard, forgot to add you to the CC list in the commits. :(
Cupertino Miranda writes:
> Hi everyone,
>
> This is the third series of these patches.
> Thank you Eduard and Yonghong 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.
>
> Cupertino Miranda (6):
> 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.
>
> kernel/bpf/verifier.c | 139 ++++++++++--------
> .../selftests/bpf/progs/verifier_bounds.c | 63 ++++++++
> 2 files changed, 137 insertions(+), 65 deletions(-)
prev parent reply other threads:[~2024-04-24 22:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 22:40 [PATCH bpf-next v3 0/6] bpf/verifier: range computation improvements Cupertino Miranda
2024-04-24 22:40 ` [PATCH bpf-next v3 1/6] bpf/verifier: replace calls to mark_reg_unknown Cupertino Miranda
2024-04-25 16:56 ` Eduard Zingerman
2024-04-24 22:40 ` [PATCH bpf-next v3 2/6] bpf/verifier: refactor checks for range computation Cupertino Miranda
2024-04-25 18:49 ` Eduard Zingerman
2024-04-25 23:05 ` Andrii Nakryiko
2024-04-26 10:20 ` Cupertino Miranda
2024-04-26 16:11 ` Andrii Nakryiko
2024-04-26 16:17 ` Alexei Starovoitov
2024-04-27 22:51 ` Cupertino Miranda
2024-04-28 3:22 ` Andrii Nakryiko
2024-04-28 10:56 ` Cupertino Miranda
2024-04-24 22:40 ` [PATCH bpf-next v3 3/6] bpf/verifier: improve XOR and OR " Cupertino Miranda
2024-04-25 18:52 ` Eduard Zingerman
2024-04-24 22:40 ` [PATCH bpf-next v3 4/6] selftests/bpf: XOR and OR range computation tests Cupertino Miranda
2024-04-25 18:59 ` Eduard Zingerman
2024-04-25 23:17 ` Andrii Nakryiko
2024-04-24 22:40 ` [PATCH bpf-next v3 5/6] bpf/verifier: relax MUL range computation check Cupertino Miranda
2024-04-25 19:00 ` Eduard Zingerman
2024-04-25 23:24 ` Andrii Nakryiko
2024-04-24 22:40 ` [PATCH bpf-next v3 6/6] selftests/bpf: MUL range computation tests Cupertino Miranda
2024-04-25 19:02 ` Eduard Zingerman
2024-04-25 23:26 ` Andrii Nakryiko
2024-04-24 22:45 ` Cupertino Miranda [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=87mspi8jne.fsf@oracle.com \
--to=cupertino.miranda@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.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).