public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Workaround verification failure for fexit_bpf2bpf/func_replace_return_code
Date: Fri, 10 Mar 2023 03:20:18 +0000	[thread overview]
Message-ID: <167841841803.8288.15840600513203502382.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230310012410.2920570-1-yhs@fb.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Thu, 9 Mar 2023 17:24:10 -0800 you wrote:
> With latest llvm17, selftest fexit_bpf2bpf/func_replace_return_code
> has the following verification failure:
> 
>   0: R1=ctx(off=0,imm=0) R10=fp0
>   ; int connect_v4_prog(struct bpf_sock_addr *ctx)
>   0: (bf) r7 = r1                       ; R1=ctx(off=0,imm=0) R7_w=ctx(off=0,imm=0)
>   1: (b4) w6 = 0                        ; R6_w=0
>   ; memset(&tuple.ipv4.saddr, 0, sizeof(tuple.ipv4.saddr));
>   ...
>   ; return do_bind(ctx) ? 1 : 0;
>   179: (bf) r1 = r7                     ; R1=ctx(off=0,imm=0) R7=ctx(off=0,imm=0)
>   180: (85) call pc+147
>   Func#3 is global and valid. Skipping.
>   181: R0_w=scalar()
>   181: (bc) w6 = w0                     ; R0_w=scalar() R6_w=scalar(umax=4294967295,var_off=(0x0; 0xffffffff))
>   182: (05) goto pc-129
>   ; }
>   54: (bc) w0 = w6                      ; R0_w=scalar(umax=4294967295,var_off=(0x0; 0xffffffff)) R6_w=scalar(umax=4294967295,var_off=(0x0; 0xffffffff))
>   55: (95) exit
>   At program exit the register R0 has value (0x0; 0xffffffff) should have been in (0x0; 0x1)
>   processed 281 insns (limit 1000000) max_states_per_insn 1 total_states 26 peak_states 26 mark_read 13
>   -- END PROG LOAD LOG --
>   libbpf: prog 'connect_v4_prog': failed to load: -22
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Workaround verification failure for fexit_bpf2bpf/func_replace_return_code
    https://git.kernel.org/bpf/bpf-next/c/63d78b7e8ca2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-03-10  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  1:24 [PATCH bpf-next] selftests/bpf: Workaround verification failure for fexit_bpf2bpf/func_replace_return_code Yonghong Song
2023-03-10  3:20 ` patchwork-bot+netdevbpf [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=167841841803.8288.15840600513203502382.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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 \
    --cc=yhs@fb.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