All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org
Subject: pull-request: bpf 2019-04-04
Date: Thu,  4 Apr 2019 17:21:41 +0200	[thread overview]
Message-ID: <20190404152141.19803-1-daniel@iogearbox.net> (raw)

Hi David,

The following pull-request contains BPF updates for your *net* tree.

The main changes are:

1) Batch of fixes to the existing BPF flow dissector API to support
   calling BPF programs from the eth_get_headlen context (support for
   latter is planned to be added in bpf-next), from Stanislav.

Please consider pulling these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

Thanks a lot!

----------------------------------------------------------------

The following changes since commit b2e54b09a3d29c4db883b920274ca8dca4d9f04d:

  ip6_tunnel: Match to ARPHRD_TUNNEL6 for dev type (2019-04-02 13:19:34 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 

for you to fetch changes up to 5eed7898626bedd6405421550c0c6e8ab9591bb2:

  flow_dissector: rst'ify documentation (2019-04-04 15:25:23 +0200)

----------------------------------------------------------------
Daniel Borkmann (1):
      Merge branch 'bpf-flow-dissector-fixes'

Stanislav Fomichev (6):
      selftests/bpf: fix vlan handling in flow dissector program
      net/flow_dissector: pass flow_keys->n_proto to BPF programs
      flow_dissector: fix clamping of BPF flow_keys for non-zero nhoff
      flow_dissector: allow access only to a subset of __sk_buff fields
      flow_dissector: document BPF flow dissector environment
      flow_dissector: rst'ify documentation

 Documentation/networking/bpf_flow_dissector.rst    | 126 +++++++++++++++++++++
 Documentation/networking/index.rst                 |   1 +
 net/core/filter.c                                  |  16 +--
 net/core/flow_dissector.c                          |   4 +-
 .../selftests/bpf/prog_tests/flow_dissector.c      |  68 +++++++++++
 tools/testing/selftests/bpf/progs/bpf_flow.c       |  19 ++--
 6 files changed, 208 insertions(+), 26 deletions(-)
 create mode 100644 Documentation/networking/bpf_flow_dissector.rst

             reply	other threads:[~2019-04-04 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 15:21 Daniel Borkmann [this message]
2019-04-05  0:05 ` pull-request: bpf 2019-04-04 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=20190404152141.19803-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.