netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: ast@kernel.org
Cc: netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf-next 0/2] Few BPF kselftest improvements
Date: Mon, 26 Feb 2018 22:34:31 +0100	[thread overview]
Message-ID: <cover.1519680589.git.daniel@iogearbox.net> (raw)

First one unifies the often repeated rlimit handling and the
second one enables and adds run-time tests for BPF tail calls
which provides useful coverage in particular for JITs.

Thanks!

Daniel Borkmann (2):
  bpf: unify rlimit handling in selftests
  bpf: add tail call tests to test_verifier

 tools/testing/selftests/bpf/bpf_rlimit.h        |  28 ++++++
 tools/testing/selftests/bpf/test_align.c        |   6 +-
 tools/testing/selftests/bpf/test_dev_cgroup.c   |   6 +-
 tools/testing/selftests/bpf/test_lpm_map.c      |  14 +--
 tools/testing/selftests/bpf/test_lru_map.c      |   6 +-
 tools/testing/selftests/bpf/test_maps.c         |   7 +-
 tools/testing/selftests/bpf/test_progs.c        |   7 +-
 tools/testing/selftests/bpf/test_tag.c          |   4 +-
 tools/testing/selftests/bpf/test_tcpbpf_user.c  |   6 +-
 tools/testing/selftests/bpf/test_verifier.c     | 123 +++++++++++++++++++++---
 tools/testing/selftests/bpf/test_verifier_log.c |   8 +-
 11 files changed, 154 insertions(+), 61 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/bpf_rlimit.h

-- 
2.9.5

             reply	other threads:[~2018-02-26 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 21:34 Daniel Borkmann [this message]
2018-02-26 21:34 ` [PATCH bpf-next 1/2] bpf: unify rlimit handling in selftests Daniel Borkmann
2018-02-26 21:34 ` [PATCH bpf-next 2/2] bpf: add tail call tests to test_verifier Daniel Borkmann
2018-02-27  4:16 ` [PATCH bpf-next 0/2] Few BPF kselftest improvements Alexei Starovoitov

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=cover.1519680589.git.daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --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).