From: Gary Lin <glin@suse.com>
To: netdev@vger.kernel.org, bpf@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
andreas.taschner@suse.com
Subject: [PATCH RESEND v2 0/3] bpf,x64: implement jump padding in jit
Date: Thu, 7 Jan 2021 10:16:58 +0800 [thread overview]
Message-ID: <20210107021701.1797-1-glin@suse.com> (raw)
This patch series implements jump padding to x64 jit to cover some
corner cases that used to consume more than 20 passes and caused
failure.
v2:
- Simplify the sample code in the commit description and provide the
jit code
- Check the expected padding bytes with WARN_ONCE
- Move the 'padded' flag to 'struct x64_jit_data'
- Remove the EXPECTED_FAIL flag from bpf_fill_maxinsns11() in test_bpf
- Add 2 verifier tests
Gary Lin (3):
bpf,x64: pad NOPs to make images converge more easily
test_bpf: remove EXPECTED_FAIL flag from bpf_fill_maxinsns11
selftests/bpf: Add verifier test for x64 jit jump padding
arch/x86/net/bpf_jit_comp.c | 86 +++++++++++++++------
lib/test_bpf.c | 7 +-
tools/testing/selftests/bpf/test_verifier.c | 43 +++++++++++
tools/testing/selftests/bpf/verifier/jit.c | 16 ++++
4 files changed, 122 insertions(+), 30 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-07 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 2:16 Gary Lin [this message]
2021-01-07 2:16 ` [PATCH RESEND v2 1/3] bpf,x64: pad NOPs to make images converge more easily Gary Lin
2021-01-08 22:21 ` Daniel Borkmann
2021-01-11 6:22 ` Gary Lin
2021-01-07 2:17 ` [PATCH RESEND v2 2/3] test_bpf: remove EXPECTED_FAIL flag from bpf_fill_maxinsns11 Gary Lin
2021-01-07 2:17 ` [PATCH RESEND v2 3/3] selftests/bpf: Add verifier test for x64 jit jump padding 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=20210107021701.1797-1-glin@suse.com \
--to=glin@suse.com \
--cc=andreas.taschner@suse.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eric.dumazet@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.