mbox series

[bpf-next,V16,0/7] bpf: New approach for BPF MTU handling

Message ID 161287779408.790810.15631860742170694244.stgit@firesoul (mailing list archive)
Headers show
Series bpf: New approach for BPF MTU handling | expand

Message

Jesper Dangaard Brouer Feb. 9, 2021, 1:38 p.m. UTC
This patchset drops all the MTU checks in TC BPF-helpers that limits
growing the packet size. This is done because these BPF-helpers doesn't
take redirect into account, which can result in their MTU check being done
against the wrong netdev.

The new approach is to give BPF-programs knowledge about the MTU on a
netdev (via ifindex) and fib route lookup level. Meaning some BPF-helpers
are added and extended to make it possible to do MTU checks in the
BPF-code.

If BPF-prog doesn't comply with the MTU then the packet will eventually
get dropped as some other layer. In some cases the existing kernel MTU
checks will drop the packet, but there are also cases where BPF can bypass
these checks. Specifically doing TC-redirect from ingress step
(sch_handle_ingress) into egress code path (basically calling
dev_queue_xmit()). It is left up to driver code to handle these kind of
MTU violations.

One advantage of this approach is that it ingress-to-egress BPF-prog can
send information via packet data. With the MTU checks removed in the
helpers, and also not done in skb_do_redirect() call, this allows for an
ingress BPF-prog to communicate with an egress BPF-prog via packet data,
as long as egress BPF-prog remove this prior to transmitting packet.

This patchset is primarily focused on TC-BPF, but I've made sure that the
MTU BPF-helpers also works for XDP BPF-programs.

V2: Change BPF-helper API from lookup to check.
V3: Drop enforcement of MTU in net-core, leave it to drivers.
V4: Keep sanity limit + netdev "up" checks + rename BPF-helper.
V5: Fix uninit variable + name struct output member mtu_result.
V6: Use bpf_check_mtu() in selftest
V7: Fix logic using tot_len and add another selftest
V8: Add better selftests for BPF-helper bpf_check_mtu
V9: Remove patch that use skb_set_redirected
V10: Fix selftests and 'tot_len' MTU check like XDP
V11: Fix nitpicks in selftests
V12: Adjustments requested by Daniel
V13: More adjustments requested by Daniel
V14: Improve man page for BPF-helper bpf_check_mtu
V15: Missing static for a function declaration
V16: Revert part of V13 in patch 2
---
Feel free to trim version comments before applying.

Jesper Dangaard Brouer (7):
      bpf: Remove MTU check in __bpf_skb_max_len
      bpf: fix bpf_fib_lookup helper MTU check for SKB ctx
      bpf: bpf_fib_lookup return MTU value as output when looked up
      bpf: add BPF-helper for MTU checking
      bpf: drop MTU check when doing TC-BPF redirect to ingress
      selftests/bpf: use bpf_check_mtu in selftest test_cls_redirect
      selftests/bpf: tests using bpf_check_mtu BPF-helper


 include/linux/netdevice.h                          |   32 +++
 include/uapi/linux/bpf.h                           |   86 ++++++++
 net/core/dev.c                                     |   32 +--
 net/core/filter.c                                  |  167 ++++++++++++++-
 tools/include/uapi/linux/bpf.h                     |   86 ++++++++
 tools/testing/selftests/bpf/prog_tests/check_mtu.c |  216 ++++++++++++++++++++
 tools/testing/selftests/bpf/progs/test_check_mtu.c |  198 ++++++++++++++++++
 .../selftests/bpf/progs/test_cls_redirect.c        |    7 +
 8 files changed, 779 insertions(+), 45 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/prog_tests/check_mtu.c
 create mode 100644 tools/testing/selftests/bpf/progs/test_check_mtu.c

--

Comments

patchwork-bot+netdevbpf@kernel.org Feb. 13, 2021, 12:20 a.m. UTC | #1
Hello:

This series was applied to bpf/bpf-next.git (refs/heads/master):

On Tue, 09 Feb 2021 14:38:04 +0100 you wrote:
> This patchset drops all the MTU checks in TC BPF-helpers that limits
> growing the packet size. This is done because these BPF-helpers doesn't
> take redirect into account, which can result in their MTU check being done
> against the wrong netdev.
> 
> The new approach is to give BPF-programs knowledge about the MTU on a
> netdev (via ifindex) and fib route lookup level. Meaning some BPF-helpers
> are added and extended to make it possible to do MTU checks in the
> BPF-code.
> 
> [...]

Here is the summary with links:
  - [bpf-next,V16,1/7] bpf: Remove MTU check in __bpf_skb_max_len
    https://git.kernel.org/bpf/bpf-next/c/6306c1189e77
  - [bpf-next,V16,2/7] bpf: fix bpf_fib_lookup helper MTU check for SKB ctx
    https://git.kernel.org/bpf/bpf-next/c/2c0a10af688c
  - [bpf-next,V16,3/7] bpf: bpf_fib_lookup return MTU value as output when looked up
    https://git.kernel.org/bpf/bpf-next/c/e1850ea9bd9e
  - [bpf-next,V16,4/7] bpf: add BPF-helper for MTU checking
    https://git.kernel.org/bpf/bpf-next/c/34b2021cc616
  - [bpf-next,V16,5/7] bpf: drop MTU check when doing TC-BPF redirect to ingress
    https://git.kernel.org/bpf/bpf-next/c/5f7d57280c19
  - [bpf-next,V16,6/7] selftests/bpf: use bpf_check_mtu in selftest test_cls_redirect
    https://git.kernel.org/bpf/bpf-next/c/6b8838be7e21
  - [bpf-next,V16,7/7] selftests/bpf: tests using bpf_check_mtu BPF-helper
    https://git.kernel.org/bpf/bpf-next/c/b62eba563229

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html