From: Ido Schimmel <idosch@nvidia.com>
To: Anton Danilov <littlesmilingcloud@gmail.com>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>, Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 07/10] ip_tunnel: add drop reasons to the transmit path
Date: Wed, 23 Sep 2026 18:53:39 +0300 [thread overview]
Message-ID: <20260923155339.GB2880695@shredder> (raw)
In-Reply-To: <20260922221507.3268127-8-littlesmilingcloud@gmail.com>
On Wed, Sep 23, 2026 at 01:15:04AM +0300, Anton Danilov wrote:
> @@ -711,9 +721,15 @@ void ip_tunnel_xmit(struct sk_buff *skb, struct net_device *dev,
>
> if (!skb_dst(skb)) {
> DEV_STATS_INC(dev, tx_fifo_errors);
> + reason = SKB_DROP_REASON_NO_TX_TARGET;
> goto tx_error;
> }
>
> + /* Only the branches below can derive a destination. If
> + * none of them matches, the payload protocol is not one
> + * this tunnel can carry.
> + */
> + reason = SKB_DROP_REASON_UNHANDLED_PROTO;
> tun_info = skb_tunnel_info(skb);
> if (tun_info && (tun_info->mode & IP_TUNNEL_INFO_TX) &&
> ip_tunnel_info_af(tun_info) == AF_INET &&
> @@ -734,8 +750,10 @@ void ip_tunnel_xmit(struct sk_buff *skb, struct net_device *dev,
>
> neigh = dst_neigh_lookup(skb_dst(skb),
> &ipv6_hdr(skb)->daddr);
> - if (!neigh)
> + if (!neigh) {
> + reason = SKB_DROP_REASON_NEIGH_CREATEFAIL;
> goto tx_error;
> + }
>
> addr6 = (const struct in6_addr *)&neigh->primary_key;
> addr_type = ipv6_addr_type(addr6);
> @@ -752,8 +770,10 @@ void ip_tunnel_xmit(struct sk_buff *skb, struct net_device *dev,
> dst = addr6->s6_addr32[3];
> }
> neigh_release(neigh);
> - if (do_tx_error_icmp)
> + if (do_tx_error_icmp) {
> + reason = SKB_DROP_REASON_NO_TX_TARGET;
> goto tx_error_icmp;
> + }
> }
> #endif
> else
Makes more sense:
diff --git a/net/ipv4/ip_tunnel.c b/net/ipv4/ip_tunnel.c
index 66cb0b86fa79..20b666fcca9a 100644
--- a/net/ipv4/ip_tunnel.c
+++ b/net/ipv4/ip_tunnel.c
@@ -725,11 +725,6 @@ void ip_tunnel_xmit(struct sk_buff *skb, struct net_device *dev,
goto tx_error;
}
- /* Only the branches below can derive a destination. If
- * none of them matches, the payload protocol is not one
- * this tunnel can carry.
- */
- reason = SKB_DROP_REASON_UNHANDLED_PROTO;
tun_info = skb_tunnel_info(skb);
if (tun_info && (tun_info->mode & IP_TUNNEL_INFO_TX) &&
ip_tunnel_info_af(tun_info) == AF_INET &&
@@ -776,8 +771,10 @@ void ip_tunnel_xmit(struct sk_buff *skb, struct net_device *dev,
}
}
#endif
- else
+ else {
+ reason = SKB_DROP_REASON_UNHANDLED_PROTO;
goto tx_error;
+ }
if (!md)
connected = false;
next prev parent reply other threads:[~2026-09-23 15:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 22:14 [PATCH net-next v4 00/10] tunnels: add core and gre drop reasons Anton Danilov
2026-09-22 22:14 ` [PATCH net-next v4 01/10] ip_tunnel: add drop reasons to the generic RX path Anton Danilov
2026-09-22 22:14 ` [PATCH net-next v4 02/10] ip6_tunnel: " Anton Danilov
2026-09-22 22:15 ` [PATCH net-next v4 03/10] gre: make gre_parse_header() report a drop reason Anton Danilov
2026-09-23 14:59 ` Ido Schimmel
2026-09-25 23:12 ` Anton Danilov
2026-09-22 22:15 ` [PATCH net-next v4 04/10] ip_tunnel: add __iptunnel_pull_header_reason() Anton Danilov
2026-09-23 15:41 ` Ido Schimmel
2026-09-25 23:12 ` Anton Danilov
2026-09-28 6:46 ` Ido Schimmel
2026-09-22 22:15 ` [PATCH net-next v4 05/10] ip_gre: add drop reasons to the RX path Anton Danilov
2026-09-22 22:15 ` [PATCH net-next v4 06/10] ip6_gre: " Anton Danilov
2026-09-22 22:15 ` [PATCH net-next v4 07/10] ip_tunnel: add drop reasons to the transmit path Anton Danilov
2026-09-23 15:53 ` Ido Schimmel [this message]
2026-09-22 22:15 ` [PATCH net-next v4 08/10] ip_gre: " Anton Danilov
2026-09-22 22:15 ` [PATCH net-next v4 09/10] ip6_gre: make prepare_ip6gre_xmit_other() void Anton Danilov
2026-09-22 22:15 ` [PATCH net-next v4 10/10] ip6_tunnel: add drop reasons to the transmit path Anton Danilov
2026-09-23 14:19 ` [PATCH net-next v4 00/10] tunnels: add core and gre drop reasons Ido Schimmel
2026-09-25 23:11 ` Anton Danilov
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=20260923155339.GB2880695@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=littlesmilingcloud@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.