From: Paul Chaignon <paul@isovalent.com>
To: Eyal Birger <eyal.birger@gmail.com>,
idosch@nvidia.com, petrm@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, razor@blackwall.org,
daniel@iogearbox.net, kafai@fb.com
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf] ip_tunnel: respect tunnel key's "flow_flags" in IP tunnels
Date: Thu, 18 Aug 2022 15:32:09 +0200 [thread overview]
Message-ID: <20220818133209.GA80579@Mem> (raw)
In-Reply-To: <20220818074118.726639-1-eyal.birger@gmail.com>
On Thu, Aug 18, 2022 at 10:41:18AM +0300, Eyal Birger wrote:
> Commit 451ef36bd229 ("ip_tunnels: Add new flow flags field to ip_tunnel_key")
> added a "flow_flags" member to struct ip_tunnel_key which was later used by
> the commit in the fixes tag to avoid dropping packets with sources that
> aren't locally configured when set in bpf_set_tunnel_key().
>
> VXLAN and GENEVE were made to respect this flag, ip tunnels like IPIP and GRE
> were not.
>
> This commit fixes this omission by making ip_tunnel_init_flow() receive
> the flow flags from the tunnel key in the relevant collect_md paths.
>
> Fixes: b8fff748521c ("bpf: Set flow flag to allow any source IP in bpf_tunnel_key")
> Signed-off-by: Eyal Birger <eyal.birger@gmail.com>
> ---
> drivers/net/ethernet/mellanox/mlxsw/spectrum_span.c | 3 ++-
> include/net/ip_tunnels.h | 4 +++-
> net/ipv4/ip_gre.c | 2 +-
> net/ipv4/ip_tunnel.c | 7 ++++---
> 4 files changed, 10 insertions(+), 6 deletions(-)
Thanks for the fix!
Reviewed-by: Paul Chaignon <paul@isovalent.com>
next prev parent reply other threads:[~2022-08-18 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 7:41 [PATCH bpf] ip_tunnel: respect tunnel key's "flow_flags" in IP tunnels Eyal Birger
2022-08-18 13:32 ` Paul Chaignon [this message]
2022-08-18 19:30 ` patchwork-bot+netdevbpf
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=20220818133209.GA80579@Mem \
--to=paul@isovalent.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=idosch@nvidia.com \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=yoshfuji@linux-ipv6.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.