From: Ido Schimmel <idosch@nvidia.com>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, dsahern@kernel.org, dongml2@chinatelecom.cn,
amcohen@nvidia.com, gnault@redhat.com, bpoirier@nvidia.com,
b.galvani@gmail.com, razor@blackwall.org, petrm@nvidia.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 06/10] net: vxlan: add skb drop reasons to vxlan_rcv()
Date: Tue, 20 Aug 2024 15:26:55 +0300 [thread overview]
Message-ID: <ZsSLj-fI5Hiy9aV-@shredder.mtl.com> (raw)
In-Reply-To: <20240815124302.982711-7-dongml2@chinatelecom.cn>
On Thu, Aug 15, 2024 at 08:42:58PM +0800, Menglong Dong wrote:
> diff --git a/drivers/net/vxlan/vxlan_core.c b/drivers/net/vxlan/vxlan_core.c
> index e971c4785962..9a61f04bb95d 100644
> --- a/drivers/net/vxlan/vxlan_core.c
> +++ b/drivers/net/vxlan/vxlan_core.c
> @@ -1668,6 +1668,7 @@ static bool vxlan_ecn_decapsulate(struct vxlan_sock *vs, void *oiph,
> /* Callback from net/ipv4/udp.c to receive packets */
> static int vxlan_rcv(struct sock *sk, struct sk_buff *skb)
> {
> + enum skb_drop_reason reason = pskb_may_pull_reason(skb, VXLAN_HLEN);
> struct vxlan_vni_node *vninode = NULL;
> struct vxlan_dev *vxlan;
> struct vxlan_sock *vs;
> @@ -1681,7 +1682,7 @@ static int vxlan_rcv(struct sock *sk, struct sk_buff *skb)
> int nh;
>
> /* Need UDP and VXLAN header to be present */
> - if (!pskb_may_pull(skb, VXLAN_HLEN))
> + if (reason != SKB_NOT_DROPPED_YET)
> goto drop;
>
> unparsed = *vxlan_hdr(skb);
> @@ -1690,6 +1691,7 @@ static int vxlan_rcv(struct sock *sk, struct sk_buff *skb)
> netdev_dbg(skb->dev, "invalid vxlan flags=%#x vni=%#x\n",
> ntohl(vxlan_hdr(skb)->vx_flags),
> ntohl(vxlan_hdr(skb)->vx_vni));
> + reason = (u32)VXLAN_DROP_FLAGS;
I don't find "FLAGS" very descriptive. AFAICT the reason is used in
these two cases:
1. "I flag" is not set
2. The reserved fields are not zero
Maybe call it VXLAN_DROP_INVALID_HDR ?
And I agree with the comment about documenting these drop reasons like
in include/net/dropreason-core.h
> /* Return non vxlan pkt */
> goto drop;
> }
> @@ -1703,8 +1705,10 @@ static int vxlan_rcv(struct sock *sk, struct sk_buff *skb)
> vni = vxlan_vni(vxlan_hdr(skb)->vx_vni);
>
> vxlan = vxlan_vs_find_vni(vs, skb->dev->ifindex, vni, &vninode);
> - if (!vxlan)
> + if (!vxlan) {
> + reason = (u32)VXLAN_DROP_VNI;
Same comment here. Maybe VXLAN_DROP_VNI_NOT_FOUND ?
> goto drop;
> + }
>
> /* For backwards compatibility, only allow reserved fields to be
> * used by VXLAN extensions if explicitly requested.
> @@ -1717,12 +1721,16 @@ static int vxlan_rcv(struct sock *sk, struct sk_buff *skb)
> }
>
> if (__iptunnel_pull_header(skb, VXLAN_HLEN, protocol, raw_proto,
> - !net_eq(vxlan->net, dev_net(vxlan->dev))))
> + !net_eq(vxlan->net, dev_net(vxlan->dev)))) {
> + reason = SKB_DROP_REASON_NOMEM;
> goto drop;
> + }
>
> - if (vs->flags & VXLAN_F_REMCSUM_RX)
> - if (unlikely(!vxlan_remcsum(&unparsed, skb, vs->flags)))
> + if (vs->flags & VXLAN_F_REMCSUM_RX) {
> + reason = vxlan_remcsum(&unparsed, skb, vs->flags);
> + if (unlikely(reason != SKB_NOT_DROPPED_YET))
> goto drop;
> + }
>
> if (vxlan_collect_metadata(vs)) {
> IP_TUNNEL_DECLARE_FLAGS(flags) = { };
> @@ -1732,8 +1740,10 @@ static int vxlan_rcv(struct sock *sk, struct sk_buff *skb)
> tun_dst = udp_tun_rx_dst(skb, vxlan_get_sk_family(vs), flags,
> key32_to_tunnel_id(vni), sizeof(*md));
>
> - if (!tun_dst)
> + if (!tun_dst) {
> + reason = SKB_DROP_REASON_NOMEM;
> goto drop;
> + }
>
> md = ip_tunnel_info_opts(&tun_dst->u.tun_info);
>
> @@ -1757,12 +1767,15 @@ static int vxlan_rcv(struct sock *sk, struct sk_buff *skb)
> * is more robust and provides a little more security in
> * adding extensions to VXLAN.
> */
> + reason = (u32)VXLAN_DROP_FLAGS;
> goto drop;
> }
>
> if (!raw_proto) {
> - if (!vxlan_set_mac(vxlan, vs, skb, vni))
> + if (!vxlan_set_mac(vxlan, vs, skb, vni)) {
> + reason = (u32)VXLAN_DROP_MAC;
The function drops the packet for various reasons:
1. Source MAC is equal to the VXLAN device's MAC
2. Source MAC is invalid (all zeroes or multicast)
3. Trying to migrate a static entry or one pointing to a nexthop
They are all quite obscure so it might be fine to fold them under the
same reason, but I can't find a descriptive name.
If you split 1-2 to one reason and 3 to another, then they can become
VXLAN_DROP_INVALID_SMAC and VXLAN_DROP_ENTRY_EXISTS
> goto drop;
> + }
next prev parent reply other threads:[~2024-08-20 12:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 12:42 [PATCH net-next 00/10] net: vxlan: add skb drop reasons support Menglong Dong
2024-08-15 12:42 ` [PATCH net-next 01/10] net: vxlan: add vxlan to the drop reason subsystem Menglong Dong
2024-08-15 12:42 ` [PATCH net-next 02/10] net: skb: add SKB_DR_RESET Menglong Dong
2024-08-20 12:24 ` Ido Schimmel
2024-08-21 12:55 ` Menglong Dong
2024-08-15 12:42 ` [PATCH net-next 03/10] net: skb: introduce pskb_network_may_pull_reason() Menglong Dong
2024-08-15 12:42 ` [PATCH net-next 04/10] net: ip: introduce pskb_inet_may_pull_reason() Menglong Dong
2024-08-15 12:42 ` [PATCH net-next 05/10] net: vxlan: make vxlan_remcsum() return skb drop reasons Menglong Dong
2024-08-15 12:42 ` [PATCH net-next 06/10] net: vxlan: add skb drop reasons to vxlan_rcv() Menglong Dong
2024-08-17 2:22 ` Jakub Kicinski
2024-08-17 11:33 ` Menglong Dong
2024-08-19 22:59 ` Jakub Kicinski
2024-08-21 12:51 ` Menglong Dong
2024-08-20 12:26 ` Ido Schimmel [this message]
2024-08-21 12:54 ` Menglong Dong
2024-08-15 12:42 ` [PATCH net-next 07/10] net: vxlan: use vxlan_kfree_skb() in vxlan_xmit() Menglong Dong
2024-08-20 12:28 ` Ido Schimmel
2024-08-21 12:57 ` Menglong Dong
2024-08-15 12:43 ` [PATCH net-next 08/10] net: vxlan: add drop reasons support to vxlan_xmit_one() Menglong Dong
2024-08-20 12:33 ` Ido Schimmel
2024-08-21 13:02 ` Menglong Dong
2024-08-15 12:43 ` [PATCH net-next 09/10] net: vxlan: use kfree_skb_reason in vxlan_encap_bypass Menglong Dong
2024-08-15 12:43 ` [PATCH net-next 10/10] net: vxlan: use vxlan_kfree_skb in encap_bypass_if_local Menglong Dong
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=ZsSLj-fI5Hiy9aV-@shredder.mtl.com \
--to=idosch@nvidia.com \
--cc=amcohen@nvidia.com \
--cc=b.galvani@gmail.com \
--cc=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=dongml2@chinatelecom.cn \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®