netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [RFC PATCH v2 net-next 00/10] bpf: rewrite value tracking in verifier
@ 2017-06-15 14:34 Edward Cree via iovisor-dev
  2017-06-15 14:36 ` [RFC PATCH v2 net-next 01/10] selftests/bpf: add test for mixed signed and unsigned bounds checks Edward Cree
                   ` (6 more replies)
  0 siblings, 7 replies; 11+ messages in thread
From: Edward Cree via iovisor-dev @ 2017-06-15 14:34 UTC (permalink / raw)
  To: davem-fT/PcQaiUtIeIZ0/mPfg9Q, Alexei Starovoitov,
	Alexei Starovoitov, Daniel Borkmann
  Cc: netdev-u79uwXL29TY76Z2rM5mHXA, iovisor-dev

This series simplifies alignment tracking, generalises bounds tracking and
 fixes some bounds-tracking bugs in the BPF verifier.  Pointer arithmetic on
 packet pointers, stack pointers, map value pointers and context pointers has
 been unified, and bounds on these pointers are only checked when the pointer
 is dereferenced.
Operations on pointers which destroy all relation to the original pointer
 (such as multiplies and shifts) are disallowed if !env->allow_ptr_leaks,
 otherwise they convert the pointer to an unknown scalar and feed it to the
 normal scalar arithmetic handling.
Pointer types have been unified with the corresponding adjusted-pointer types
 where those existed (e.g. PTR_TO_MAP_VALUE[_ADJ] or FRAME_PTR vs
 PTR_TO_STACK); similarly, CONST_IMM and UNKNOWN_VALUE have been unified into
 SCALAR_VALUE.
Pointer types (except CONST_PTR_TO_MAP, PTR_TO_MAP_VALUE_OR_NULL and
 PTR_TO_PACKET_END, which do not allow arithmetic) have a 'fixed offset' and
 a 'variable offset'; the former is used when e.g. adding an immediate or a
 known-constant register, as long as it does not overflow.  Otherwise the
 latter is used, and any operation creating a new variable offset creates a
 new 'id' (and, for PTR_TO_PACKET, clears the 'range').
SCALAR_VALUEs use the 'variable offset' fields to track the range of possible
 values; the 'fixed offset' should never be set on a scalar.

Patch 2/10 is rather on the big side, but since it changes the contents and
 semantics of a fairly central data structure, I'm not really sure how to go
 about splitting it up further without producing broken intermediate states.
It also breaks building the 'nfp' driver, which is fixed in patch 3/10;
 should I squash these together to preserve bisectability?

As of patch 10/10, all tests of tools/testing/selftests/bpf/test_verifier
 and tools/testing/selftests/bpf/test_align pass.

v2: fixed nfp build, made test_align pass again and extended it with a few
 new tests (though still need to add more).

Edward Cree (10):
  selftests/bpf: add test for mixed signed and unsigned bounds checks
  bpf/verifier: rework value tracking
  nfp: change bpf verifier hooks to match new verifier data structures
  bpf/verifier: track signed and unsigned min/max values
  bpf/verifier: more concise register state logs for constant var_off
  selftests/bpf: change test_verifier expectations
  selftests/bpf: rewrite test_align
  selftests/bpf: add a test to test_align
  selftests/bpf: add test for bogus operations on pointers
  selftests/bpf: don't try to access past MAX_PACKET_OFF in
    test_verifier

 drivers/net/ethernet/netronome/nfp/bpf/verifier.c |   24 +-
 include/linux/bpf.h                               |   34 +-
 include/linux/bpf_verifier.h                      |   56 +-
 include/linux/tnum.h                              |   81 +
 kernel/bpf/Makefile                               |    2 +-
 kernel/bpf/tnum.c                                 |  180 ++
 kernel/bpf/verifier.c                             | 1941 ++++++++++++---------
 tools/testing/selftests/bpf/test_align.c          |  358 +++-
 tools/testing/selftests/bpf/test_verifier.c       |  252 +--
 9 files changed, 1887 insertions(+), 1041 deletions(-)
 create mode 100644 include/linux/tnum.h
 create mode 100644 kernel/bpf/tnum.c

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2017-06-15 14:38 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-06-15 14:34 [RFC PATCH v2 net-next 00/10] bpf: rewrite value tracking in verifier Edward Cree via iovisor-dev
2017-06-15 14:36 ` [RFC PATCH v2 net-next 01/10] selftests/bpf: add test for mixed signed and unsigned bounds checks Edward Cree
2017-06-15 14:36 ` [RFC PATCH v2 net-next 02/10] bpf/verifier: rework value tracking Edward Cree
2017-06-15 14:36 ` [RFC PATCH v2 net-next 03/10] nfp: change bpf verifier hooks to match new verifier data structures Edward Cree
     [not found] ` <87861693-dbcd-c026-a1b4-8c27c2a90735-s/n/eUQHGBpZroRs9YW3xA@public.gmane.org>
2017-06-15 14:37   ` [RFC PATCH v2 net-next 04/10] bpf/verifier: track signed and unsigned min/max values Edward Cree via iovisor-dev
2017-06-15 14:37   ` [RFC PATCH v2 net-next 05/10] bpf/verifier: more concise register state logs for constant var_off Edward Cree via iovisor-dev
2017-06-15 14:38   ` [RFC PATCH v2 net-next 08/10] selftests/bpf: add a test to test_align Edward Cree via iovisor-dev
2017-06-15 14:38   ` [RFC PATCH v2 net-next 10/10] selftests/bpf: don't try to access past MAX_PACKET_OFF in test_verifier Edward Cree via iovisor-dev
2017-06-15 14:37 ` [RFC PATCH v2 net-next 06/10] selftests/bpf: change test_verifier expectations Edward Cree
2017-06-15 14:37 ` [RFC PATCH v2 net-next 07/10] selftests/bpf: rewrite test_align Edward Cree
2017-06-15 14:38 ` [RFC PATCH v2 net-next 09/10] selftests/bpf: add test for bogus operations on pointers Edward Cree

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).