From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrei Matei <andreimatei1@gmail.com>,
bpf@vger.kernel.org, andrii.nakryiko@gmail.com
Cc: sunhao.th@gmail.com, kernel-team@dataexmachina.dev
Subject: Re: [PATCH bpf v2 2/2] bpf: new verifier tests for stack access
Date: Tue, 28 Nov 2023 03:23:11 +0200 [thread overview]
Message-ID: <de2946da3720afdde07aadcda1992e3f877cca70.camel@gmail.com> (raw)
In-Reply-To: <20231126015045.1092826-3-andreimatei1@gmail.com>
On Sat, 2023-11-25 at 20:50 -0500, Andrei Matei wrote:
> This patch adds tests for the previous patch, checking the tracking of
> the maximum stack size and checking that accesses to uninit stack memory
> are allowed.
>
> They are a separate patch for review purposes; whoever merges them can
> consider squashing.
>
> Signed-off-by: Andrei Matei <andreimatei1@gmail.com>
> ---
I think the strategy now is to add new tests using inline assembly,
e.g. as a part of verifier_* tests in test_progs.
next prev parent reply other threads:[~2023-11-28 1:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 1:50 [PATCH bpf v2 0/2] bpf: fix accesses to uninit stack slots Andrei Matei
2023-11-26 1:50 ` [PATCH bpf v2 1/2] " Andrei Matei
2023-11-28 1:33 ` Eduard Zingerman
2023-11-28 1:43 ` Eduard Zingerman
2023-11-28 14:14 ` Eduard Zingerman
2023-11-29 6:05 ` Andrii Nakryiko
2023-11-29 16:48 ` Andrei Matei
2023-11-29 23:54 ` Andrii Nakryiko
2023-12-02 22:41 ` Andrei Matei
2023-11-26 1:50 ` [PATCH bpf v2 2/2] bpf: new verifier tests for stack access Andrei Matei
2023-11-28 1:23 ` Eduard Zingerman [this message]
2023-11-28 3:15 ` Andrei Matei
2023-11-28 12:55 ` Eduard Zingerman
2023-11-29 6:12 ` Andrii Nakryiko
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=de2946da3720afdde07aadcda1992e3f877cca70.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andreimatei1@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@dataexmachina.dev \
--cc=sunhao.th@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