public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: Hao Sun <sunhao.th@gmail.com>, bpf@vger.kernel.org
Cc: willemb@google.com, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, eddyz87@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] selftests/bpf: Add tests for alu on PTR_TO_FLOW_KEYS
Date: Fri, 12 Jan 2024 10:14:36 -0800	[thread overview]
Message-ID: <ea5b102e-2a4e-4363-a1d4-28e050ac9e1a@linux.dev> (raw)
In-Reply-To: <20240112152011.6264-2-sunhao.th@gmail.com>


On 1/12/24 7:20 AM, Hao Sun wrote:
> Add two cases for PTR_TO_FLOW_KEYS alu. One for rejecting alu with
> variable offset, another for fixed offset.
>
> Signed-off-by: Hao Sun <sunhao.th@gmail.com>
> ---
>   .../bpf/progs/verifier_value_illegal_alu.c    | 36 +++++++++++++++++++
>   1 file changed, 36 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/progs/verifier_value_illegal_alu.c b/tools/testing/selftests/bpf/progs/verifier_value_illegal_alu.c
> index 71814a753216..3bcccb4cbc85 100644
> --- a/tools/testing/selftests/bpf/progs/verifier_value_illegal_alu.c
> +++ b/tools/testing/selftests/bpf/progs/verifier_value_illegal_alu.c
> @@ -146,4 +146,40 @@ l0_%=:	exit;						\
>   	: __clobber_all);
>   }
>   
> +SEC("flow_dissector")
> +__description("flow_keys illegal alu op with variable offset")
> +__failure __msg("R7 pointer arithmetic on flow_keys prohibited")
> +__naked void flow_keys_illegal_variable_offset_alu(void)
> +{
> +	asm volatile("					\
> +	r6 = r1;					\
> +	r7 = *(u64*)(r6 + %[flow_keys_off]);		\
> +	r8 = 8;						\
> +	r8 /= 1;					\
> +	r8 &= 8;					\
> +	r7 += r8;					\
> +	r0 = *(u64*)(r7 + 0);				\
> +	exit;						\
> +"	:
> +	: __imm_const(flow_keys_off, offsetof(struct __sk_buff, flow_keys))
> +	: __clobber_all);
> +}
> +
> +SEC("flow_dissector")
> +__description("flow_keys valid alu op with fixed offset")
> +__success
> +__naked void flow_keys_legal_fixed_offset_alu(void)
> +{
> +	asm volatile("					\
> +	r6 = r1;					\
> +	r7 = *(u64*)(r6 + %[flow_keys_off]);		\
> +	r8 = 8;						\
> +	r7 += r8;					\
> +	r0 = *(u64*)(r7 + 0);				\
> +	exit;						\
> +"	:
> +	: __imm_const(flow_keys_off, offsetof(struct __sk_buff, flow_keys))
> +	: __clobber_all);
> +}

Please remove the above '__success' case from this file. This file,
verifier_value_illegal_alu.c, only contains failure cases.

For the fixed offset, we already have C code to verify,
e.g., in bpf_flow.c.


  reply	other threads:[~2024-01-12 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 15:20 [PATCH v3 1/2] bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS Hao Sun
2024-01-12 15:20 ` [PATCH v3 2/2] selftests/bpf: Add tests for " Hao Sun
2024-01-12 18:14   ` Yonghong Song [this message]
2024-01-12 17:56 ` [PATCH v3 1/2] bpf: Reject variable offset " Alexei Starovoitov
2024-01-12 18:02   ` Hao Sun
2024-01-12 18:38 ` 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=ea5b102e-2a4e-4363-a1d4-28e050ac9e1a@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=eddyz87@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sunhao.th@gmail.com \
    --cc=willemb@google.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