From: "Björn Töpel" <bjorn.topel@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org
Cc: "Björn Töpel" <bjorn.topel@gmail.com>,
xi.wang@gmail.com, luke.r.nels@gmail.com,
linux-riscv@lists.infradead.org, andrii.nakryiko@gmail.com
Subject: [PATCH bpf-next v2 0/3] RISC-V selftest/bpf fixes
Date: Wed, 18 Nov 2020 08:16:37 +0100 [thread overview]
Message-ID: <20201118071640.83773-1-bjorn.topel@gmail.com> (raw)
This series contain some fixes for selftests/bpf when building/running
on a RISC-V host. Details can be found in each individual commit.
Cheers,
Björn
v2:
Makefile cosmetics. (Andrii)
Simplified unpriv check and added comment. (Andrii)
Björn Töpel (3):
selftests/bpf: Fix broken riscv build
selftests/bpf: Avoid running unprivileged tests with alignment
requirements
selftests/bpf: Mark tests that require unaligned memory access
tools/testing/selftests/bpf/Makefile | 3 +-
tools/testing/selftests/bpf/test_verifier.c | 13 ++++++
.../selftests/bpf/verifier/ctx_sk_lookup.c | 7 +++
.../bpf/verifier/direct_value_access.c | 3 ++
.../testing/selftests/bpf/verifier/map_ptr.c | 1 +
.../selftests/bpf/verifier/raw_tp_writable.c | 1 +
.../selftests/bpf/verifier/ref_tracking.c | 4 ++
.../testing/selftests/bpf/verifier/regalloc.c | 8 ++++
.../selftests/bpf/verifier/wide_access.c | 46 +++++++++++--------
9 files changed, 67 insertions(+), 19 deletions(-)
base-commit: ea87ae85c9b31303a2e9d4c769d9f3ee8a3a60d1
--
2.27.0
next reply other threads:[~2020-11-18 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 7:16 Björn Töpel [this message]
2020-11-18 7:16 ` [PATCH bpf-next v2 1/3] selftests/bpf: Fix broken riscv build Björn Töpel
2020-11-18 7:16 ` [PATCH bpf-next v2 2/3] selftests/bpf: Avoid running unprivileged tests with alignment requirements Björn Töpel
2020-11-18 7:16 ` [PATCH bpf-next v2 3/3] selftests/bpf: Mark tests that require unaligned memory access Björn Töpel
2020-11-18 17:43 ` [PATCH bpf-next v2 0/3] RISC-V selftest/bpf fixes Luke Nelson
2020-11-19 2:00 ` patchwork-bot+netdevbpf
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=20201118071640.83773-1-bjorn.topel@gmail.com \
--to=bjorn.topel@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xi.wang@gmail.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;
as well as URLs for NNTP newsgroup(s).