bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
	borkmann@iogearbox.net, alexei.starovoitov@gmail.com,
	maze@google.com, lmb@cloudflare.com, shaun@tigera.io,
	lorenzo@kernel.org, marek@cloudflare.com,
	john.fastabend@gmail.com, kuba@kernel.org, eyal.birger@gmail.com,
	colrack@gmail.com
Subject: Re: [PATCH bpf-next V16 0/7] bpf: New approach for BPF MTU handling
Date: Sat, 13 Feb 2021 00:20:09 +0000	[thread overview]
Message-ID: <161317560922.26527.12147444743341964387.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <161287779408.790810.15631860742170694244.stgit@firesoul>

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



      parent reply	other threads:[~2021-02-13  0:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 13:38 [PATCH bpf-next V16 0/7] bpf: New approach for BPF MTU handling Jesper Dangaard Brouer
2021-02-09 13:38 ` [PATCH bpf-next V16 1/7] bpf: Remove MTU check in __bpf_skb_max_len Jesper Dangaard Brouer
2021-02-09 13:38 ` [PATCH bpf-next V16 2/7] bpf: fix bpf_fib_lookup helper MTU check for SKB ctx Jesper Dangaard Brouer
2021-02-09 13:38 ` [PATCH bpf-next V16 3/7] bpf: bpf_fib_lookup return MTU value as output when looked up Jesper Dangaard Brouer
2021-02-09 13:38 ` [PATCH bpf-next V16 4/7] bpf: add BPF-helper for MTU checking Jesper Dangaard Brouer
2021-02-09 13:38 ` [PATCH bpf-next V16 5/7] bpf: drop MTU check when doing TC-BPF redirect to ingress Jesper Dangaard Brouer
2021-02-09 13:38 ` [PATCH bpf-next V16 6/7] selftests/bpf: use bpf_check_mtu in selftest test_cls_redirect Jesper Dangaard Brouer
2021-02-09 13:38 ` [PATCH bpf-next V16 7/7] selftests/bpf: tests using bpf_check_mtu BPF-helper Jesper Dangaard Brouer
2021-02-13  0:20 ` patchwork-bot+netdevbpf [this message]

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=161317560922.26527.12147444743341964387.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=borkmann@iogearbox.net \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=colrack@gmail.com \
    --cc=eyal.birger@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=lmb@cloudflare.com \
    --cc=lorenzo@kernel.org \
    --cc=marek@cloudflare.com \
    --cc=maze@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=shaun@tigera.io \
    /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).