From: Eric Dumazet <eric.dumazet@gmail.com>
To: Gary Lin <glin@suse.com>, netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
andreas.taschner@suse.com
Subject: Re: [PATCH] bpf, x64: bump the number of passes to 64
Date: Thu, 3 Dec 2020 12:20:38 +0100 [thread overview]
Message-ID: <8fbcb23d-d140-48fb-819d-61f49672d9bd@gmail.com> (raw)
In-Reply-To: <20201203091252.27604-1-glin@suse.com>
On 12/3/20 10:12 AM, Gary Lin wrote:
> The x64 bpf jit expects bpf images converge within the given passes, but
> it could fail to do so with some corner cases. For example:
>
> l0: ldh [4]
> l1: jeq #0x537d, l2, l40
> l2: ld [0]
> l3: jeq #0xfa163e0d, l4, l40
> l4: ldh [12]
> l5: ldx #0xe
> l6: jeq #0x86dd, l41, l7
> l8: ld [x+16]
> l9: ja 41
>
> [... repeated ja 41 ]
>
> l40: ja 41
> l41: ret #0
> l42: ld #len
> l43: ret a
>
> This bpf program contains 32 "ja 41" instructions which are effectively
> NOPs and designed to be replaced with valid code dynamically. Ideally,
> bpf jit should optimize those "ja 41" instructions out when translating
> the bpf instructions into x86_64 machine code. However, do_jit() can
> only remove one "ja 41" for offset==0 on each pass, so it requires at
> least 32 runs to eliminate those JMPs and exceeds the current limit of
> passes (20). In the end, the program got rejected when BPF_JIT_ALWAYS_ON
> is set even though it's legit as a classic socket filter.
>
> Since this kind of programs are usually handcrafted rather than
> generated by LLVM, those programs tend to be small. To avoid increasing
> the complexity of BPF JIT, this commit just bumps the number of passes
> to 64 as suggested by Daniel to make it less likely to fail on such cases.
>
Another idea would be to stop trying to reduce size of generated
code after a given number of passes have been attempted.
Because even a limit of 64 wont ensure all 'valid' programs can be JITed.
> Signed-off-by: Gary Lin <glin@suse.com>
> ---
> arch/x86/net/bpf_jit_comp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/net/bpf_jit_comp.c b/arch/x86/net/bpf_jit_comp.c
> index 796506dcfc42..43cc80387548 100644
> --- a/arch/x86/net/bpf_jit_comp.c
> +++ b/arch/x86/net/bpf_jit_comp.c
> @@ -2042,7 +2042,7 @@ struct bpf_prog *bpf_int_jit_compile(struct bpf_prog *prog)
> * may converge on the last pass. In such case do one more
> * pass to emit the final image.
> */
> - for (pass = 0; pass < 20 || image; pass++) {
> + for (pass = 0; pass < 64 || image; pass++) {
> proglen = do_jit(prog, addrs, image, oldproglen, &ctx);
> if (proglen <= 0) {
> out_image:
>
next prev parent reply other threads:[~2020-12-03 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 9:12 [PATCH] bpf, x64: bump the number of passes to 64 Gary Lin
2020-12-03 11:20 ` Eric Dumazet [this message]
2020-12-03 18:14 ` Alexei Starovoitov
2020-12-04 3:42 ` Gary Lin
2020-12-04 10:15 ` Gary Lin
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=8fbcb23d-d140-48fb-819d-61f49672d9bd@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=andreas.taschner@suse.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=glin@suse.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).