From: Cupertino Miranda <cupertino.miranda@oracle.com>
To: bpf@vger.kernel.org
Cc: Cupertino Miranda <cupertino.miranda@oracle.com>,
Yonghong Song <yonghong.song@linux.dev>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
David Faust <david.faust@oracle.com>,
Jose Marchesi <jose.marchesi@oracle.com>,
Elena Zannoni <elena.zannoni@oracle.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>
Subject: [PATCH bpf-next v5 0/6] bpf/verifier: range computation improvements
Date: Mon, 6 May 2024 15:18:43 +0100 [thread overview]
Message-ID: <20240506141849.185293-1-cupertino.miranda@oracle.com> (raw)
Hi everyone,
This is what I hope to be the last version. :)
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.
Changes from v4:
- Merged patch nr 7 in 2.
Cc: Yonghong Song <yonghong.song@linux.dev>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: David Faust <david.faust@oracle.com>
Cc: Jose Marchesi <jose.marchesi@oracle.com>
Cc: Elena Zannoni <elena.zannoni@oracle.com>
Cc: Eduard Zingerman <eddyz87@gmail.com>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
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 | 106 +++++++-----------
.../selftests/bpf/progs/verifier_bounds.c | 63 +++++++++++
2 files changed, 104 insertions(+), 65 deletions(-)
--
2.39.2
next reply other threads:[~2024-05-06 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 14:18 Cupertino Miranda [this message]
2024-05-06 14:18 ` [PATCH bpf-next v5 1/6] bpf/verifier: replace calls to mark_reg_unknown Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 2/6] bpf/verifier: refactor checks for range computation Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 3/6] bpf/verifier: improve XOR and OR " Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 4/6] selftests/bpf: XOR and OR range computation tests Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 5/6] bpf/verifier: relax MUL range computation check Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 6/6] selftests/bpf: MUL range computation tests Cupertino Miranda
2024-05-07 0:20 ` [PATCH bpf-next v5 0/6] bpf/verifier: range computation improvements patchwork-bot+netdevbpf
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=20240506141849.185293-1-cupertino.miranda@oracle.com \
--to=cupertino.miranda@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=elena.zannoni@oracle.com \
--cc=jose.marchesi@oracle.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).