From: Stanislav Fomichev <sdf@google.com>
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, 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] bpf: Fix a verifier bug due to incorrect branch offset comparison with cpu=v4
Date: Wed, 29 Nov 2023 11:52:16 -0800 [thread overview]
Message-ID: <ZWeWcIWpNHsSY0fK@google.com> (raw)
In-Reply-To: <20231129075409.2709587-1-yonghong.song@linux.dev>
On 11/28, Yonghong Song wrote:
> Bpf cpu=v4 support is introduced in [1] and Commit 4cd58e9af8b9
> ("bpf: Support new 32bit offset jmp instruction") added support for new
> 32bit offset jmp instruction. Unfortunately, in function
> bpf_adj_delta_to_off(), for new branch insn with 32bit offset, the offset
> (plus/minor a small delta) compares to 16-bit offset bound
> [S16_MIN, S16_MAX], which caused the following verification failure:
> $ ./test_progs-cpuv4 -t verif_scale_pyperf180
> ...
> insn 10 cannot be patched due to 16-bit range
> ...
> libbpf: failed to load object 'pyperf180.bpf.o'
> scale_test:FAIL:expect_success unexpected error: -12 (errno 12)
> #405 verif_scale_pyperf180:FAIL
>
> Note that due to recent llvm18 development, the patch [2] (already applied
> in bpf-next) needs to be applied to bpf tree for testing purpose.
>
> The fix is rather simple. For 32bit offset branch insn, the adjusted
> offset compares to [S32_MIN, S32_MAX] and then verification succeeded.
>
> [1] https://lore.kernel.org/all/20230728011143.3710005-1-yonghong.song@linux.dev
> [2] https://lore.kernel.org/bpf/20231110193644.3130906-1-yonghong.song@linux.dev
>
> Fixes: 4cd58e9af8b9 ("bpf: Support new 32bit offset jmp instruction")
> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
Acked-by: Stanislav Fomichev <sdf@google.com>
next prev parent reply other threads:[~2023-11-29 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 7:54 [PATCH bpf] bpf: Fix a verifier bug due to incorrect branch offset comparison with cpu=v4 Yonghong Song
2023-11-29 19:52 ` Stanislav Fomichev [this message]
2023-11-29 22:51 ` Daniel Borkmann
2023-11-29 23:42 ` Yonghong Song
2023-11-30 0:19 ` 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=ZWeWcIWpNHsSY0fK@google.com \
--to=sdf@google.com \
--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=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