netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: alexei.starovoitov@gmail.com, netdev@vger.kernel.org,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net v2 0/5] Various BPF fixes
Date: Thu, 25 May 2017 01:05:04 +0200	[thread overview]
Message-ID: <cover.1495665905.git.daniel@iogearbox.net> (raw)

Follow-up to fix incorrect pruning when alignment tracking is
in use and to properly clear regs after call to not leave stale
data behind, also a fix that adds bpf_clone_redirect to the
bpf_helper_changes_pkt_data helper and exposes correct map_flags
for lpm map into fdinfo. For details, please see individual
patches.

Thanks!

v1 -> v2:
  - Reworked first patch so that env->strict_alignment is the
    final indicator on whether we have to deal with strict
    alignment rather than having CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS
    checks on various locations, so only checking env->strict_alignment
    is sufficient after that. Thanks for spotting, Dave!
  - Added patch 3 and 4.
  - Rest as is.

Daniel Borkmann (5):
  bpf: fix incorrect pruning decision when alignment must be tracked
  bpf: properly reset caller saved regs after helper call and ld_abs/ind
  bpf: add bpf_clone_redirect to bpf_helper_changes_pkt_data
  bpf: fix wrong exposure of map_flags into fdinfo for lpm
  bpf: add various verifier test cases

 include/linux/filter.h                      |  10 ++
 kernel/bpf/arraymap.c                       |   1 +
 kernel/bpf/lpm_trie.c                       |   1 +
 kernel/bpf/stackmap.c                       |   1 +
 kernel/bpf/verifier.c                       |  56 +++----
 net/core/filter.c                           |   1 +
 tools/include/linux/filter.h                |  10 ++
 tools/testing/selftests/bpf/test_verifier.c | 239 +++++++++++++++++++++++++++-
 8 files changed, 285 insertions(+), 34 deletions(-)

-- 
1.9.3

             reply	other threads:[~2017-05-24 23:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 23:05 Daniel Borkmann [this message]
2017-05-24 23:05 ` [PATCH net v2 1/5] bpf: fix incorrect pruning decision when alignment must be tracked Daniel Borkmann
2017-05-24 23:05 ` [PATCH net v2 2/5] bpf: properly reset caller saved regs after helper call and ld_abs/ind Daniel Borkmann
2017-05-24 23:05 ` [PATCH net v2 3/5] bpf: add bpf_clone_redirect to bpf_helper_changes_pkt_data Daniel Borkmann
2017-05-24 23:05 ` [PATCH net v2 4/5] bpf: fix wrong exposure of map_flags into fdinfo for lpm Daniel Borkmann
2017-05-24 23:05 ` [PATCH net v2 5/5] bpf: add various verifier test cases Daniel Borkmann
2017-05-25 17:45 ` [PATCH net v2 0/5] Various BPF fixes 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.1495665905.git.daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=davem@davemloft.net \
    --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).