From: Yonghong Song <yonghong.song@linux.dev>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH bpf 2/2] selftests/bpf: Add a test to verify previous stacksafe() fix
Date: Mon, 12 Aug 2024 08:07:36 -0700 [thread overview]
Message-ID: <da2f4b7a-0284-4af2-bc45-d924de809ae9@linux.dev> (raw)
In-Reply-To: <20240812052112.3980530-1-yonghong.song@linux.dev>
On 8/11/24 10:21 PM, Yonghong Song wrote:
> A selftest is added such that without the previous patch,
> a crash can happen. With the previous patch, the test can
> run successfully. The new test is written in a way which
> mimics original crash case:
> main_prog
> static_prog_1
> static_prog_2
> where static_prog_1 has different paths to static_prog_2
> and some path has stack allocated and some other path
> does not. A stacksafe() checking in static_prog_2()
> triggered the crash.
>
> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> tools/testing/selftests/bpf/progs/iters.c | 54 +++++++++++++++++++++++
> 1 file changed, 54 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/progs/iters.c b/tools/testing/selftests/bpf/progs/iters.c
> index 16bdc3e25591..8d3b75147617 100644
> --- a/tools/testing/selftests/bpf/progs/iters.c
> +++ b/tools/testing/selftests/bpf/progs/iters.c
> @@ -1432,4 +1432,58 @@ int iter_arr_with_actual_elem_count(const void *ctx)
> return sum;
> }
>
> +__u32 upper, select_n, result;
> +__u64 global;
> +
> +static __noinline bool nest_2(char *str, int len)
Argument 'len' is not needed here. I can make the change after some
additional comments.
> +{
> + /* some insns (including branch insns) to ensure stacksafe() is triggered
> + * in nest_2(). This way, stacksafe() can compare frame associated with nest_1().
> + */
> + if (str[0] == 't')
> + return true;
> + if (str[1] == 'e')
> + return true;
> + if (str[2] == 's')
> + return true;
> + if (str[3] == 't')
> + return true;
> + return false;
> +}
> +
> +static __noinline bool nest_1(int n)
> +{
> + /* case 0: allocate stack, case 1: no allocate stack */
> + switch (n) {
> + case 0: {
> + char comm[16];
> +
> + if (bpf_get_current_comm(comm, 16))
> + return false;
> + return nest_2(comm, 16);
> + }
> + case 1:
> + return nest_2((char *)&global, sizeof(global));
> + default:
> + return false;
> + }
To triger the failure, we rely on 'case 0' is explored by the verifier first
and 'case 1' is explored later. This seems the case for llvm18 and llvm20.
> +}
> +
> +SEC("raw_tp")
> +__success
> +int iter_subprog_check_stacksafe(const void *ctx)
> +{
> + long i;
> +
> + bpf_for(i, 0, upper) {
> + if (!nest_1(select_n)) {
> + result = 1;
> + return 0;
> + }
> + }
> +
> + result = 2;
> + return 0;
> +}
> +
> char _license[] SEC("license") = "GPL";
next prev parent reply other threads:[~2024-08-12 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 5:21 [PATCH bpf 1/2] bpf: Fix a kernel verifier crash in stacksafe() Yonghong Song
2024-08-12 5:21 ` [PATCH bpf 2/2] selftests/bpf: Add a test to verify previous stacksafe() fix Yonghong Song
2024-08-12 15:07 ` Yonghong Song [this message]
2024-08-12 17:38 ` [PATCH bpf 1/2] bpf: Fix a kernel verifier crash in stacksafe() Eduard Zingerman
2024-08-12 17:44 ` Alexei Starovoitov
2024-08-12 17:47 ` Eduard Zingerman
2024-08-12 17:50 ` Alexei Starovoitov
2024-08-12 17:57 ` Eduard Zingerman
2024-08-12 19:29 ` Alexei Starovoitov
2024-08-12 19:43 ` Eduard Zingerman
2024-08-12 20:02 ` Yonghong Song
2024-08-12 18:26 ` Yonghong Song
2024-08-12 18:30 ` Eduard Zingerman
2024-08-12 18:36 ` Yonghong Song
2024-08-12 18:41 ` Eduard Zingerman
2024-08-12 19:21 ` Yonghong Song
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=da2f4b7a-0284-4af2-bc45-d924de809ae9@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
/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