From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: ast@fb.com, ecree@solarflare.com, josef@toxicpanda.com,
netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net 0/5] BPF map value adjust fix
Date: Fri, 21 Jul 2017 00:00:20 +0200 [thread overview]
Message-ID: <cover.1500586732.git.daniel@iogearbox.net> (raw)
First patch in the series is the actual fix and the remaining
patches are just updates to selftests.
Thanks!
Daniel Borkmann (4):
bpf: fix mixed signed/unsigned derived min/max value bounds
bpf: allow to specify log level and reduce it for test_verifier
bpf: fix up test cases with mixed signed/unsigned bounds
bpf: more tests for mixed signed and unsigned bounds checks
Edward Cree (1):
bpf: add test for mixed signed and unsigned bounds checks
include/linux/bpf_verifier.h | 1 +
kernel/bpf/verifier.c | 108 ++++++-
tools/lib/bpf/bpf.c | 4 +-
tools/lib/bpf/bpf.h | 2 +-
tools/testing/selftests/bpf/test_align.c | 2 +-
tools/testing/selftests/bpf/test_verifier.c | 480 +++++++++++++++++++++++++++-
6 files changed, 574 insertions(+), 23 deletions(-)
--
1.9.3
next reply other threads:[~2017-07-20 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 22:00 Daniel Borkmann [this message]
2017-07-20 22:00 ` [PATCH net 1/5] bpf: fix mixed signed/unsigned derived min/max value bounds Daniel Borkmann
2017-07-20 22:19 ` Alexei Starovoitov
2017-07-20 22:00 ` [PATCH net 2/5] bpf: allow to specify log level and reduce it for test_verifier Daniel Borkmann
2017-07-20 22:00 ` [PATCH net 3/5] bpf: fix up test cases with mixed signed/unsigned bounds Daniel Borkmann
2017-07-20 22:00 ` [PATCH net 4/5] bpf: add test for mixed signed and unsigned bounds checks Daniel Borkmann
2017-07-20 22:00 ` [PATCH net 5/5] bpf: more tests " Daniel Borkmann
2017-07-20 22:20 ` [PATCH net 0/5] BPF map value adjust fix David Miller
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.1500586732.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=josef@toxicpanda.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).