public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail•com>
To: netdev@vger•kernel.org, borkmann@iogearbox•net, ast@kernel•org
Cc: davem@davemloft•net, David Ahern <dsahern@gmail•com>
Subject: [PATCH bpf-next 0/3] bpf: Add MTU check to fib lookup helper
Date: Thu, 17 May 2018 09:09:27 -0700	[thread overview]
Message-ID: <20180517160930.25076-1-dsahern@gmail.com> (raw)

Packets that exceed the egress MTU can not be forwarded in the fast path.
Add IPv4 and IPv6 MTU helpers that take a FIB lookup result (versus the
typical dst path) and add the calls to bpf_ipv{4,6}_fib_lookup.

David Ahern (3):
  net/ipv4: Add helper to return path MTU based on fib result
  net/ipv6: Add helper to return path MTU based on fib result
  bpf: Add mtu checking to FIB forwarding helper

 include/net/ip6_fib.h   |  6 ++++++
 include/net/ip6_route.h |  3 +++
 include/net/ip_fib.h    |  2 ++
 net/core/filter.c       | 10 ++++++++++
 net/ipv4/route.c        | 31 +++++++++++++++++++++++++++++++
 net/ipv6/route.c        | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 100 insertions(+)

-- 
2.11.0

             reply	other threads:[~2018-05-17 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 16:09 David Ahern [this message]
2018-05-17 16:09 ` [PATCH bpf-next 1/3] net/ipv4: Add helper to return path MTU based on fib result David Ahern
2018-05-17 16:09 ` [PATCH bpf-next 2/3] net/ipv6: " David Ahern
2018-05-17 16:09 ` [PATCH bpf-next 3/3] bpf: Add mtu checking to FIB forwarding helper David Ahern
2018-05-17 22:22   ` Daniel Borkmann
2018-05-18  0:34     ` David Ahern
2018-05-18 14:01       ` Daniel Borkmann
2018-05-20  6:41   ` kbuild test robot
2018-05-20 11:14   ` kbuild test robot

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=20180517160930.25076-1-dsahern@gmail.com \
    --to=dsahern@gmail$(echo .)com \
    --cc=ast@kernel$(echo .)org \
    --cc=borkmann@iogearbox$(echo .)net \
    --cc=davem@davemloft$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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