From: netdev-bot+sashiko@kernel.org
To: littlesmilingcloud@gmail.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, dsahern@kernel.org,
horms@kernel.org, idosch@nvidia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/8] ip6_tunnel: add drop reasons to the generic RX path
Date: Mon, 14 Sep 2026 04:37:19 +0000 [thread overview]
Message-ID: <178936063923.22033.2072645913150981969@kernel.org> (raw)
In-Reply-To: <20260913034937.875068-3-littlesmilingcloud@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue(s) to consider:
Critical: 0 · High: 0 · Medium: 0 · Low: 1
- [Low] Commit message call-graph claim is inaccurate.
--
Verified. Report follows.
ip6_tunnel: add drop reasons to the generic RX path
This converts the five drop paths in __ip6_tnl_rcv() from a plain
kfree_skb() to kfree_skb_reason(), splitting the combined sequence number
check into two cases so the option mismatch and the old sequence number
failures can be distinguished, and propagating the reasons already returned
by pskb_may_pull_reason() and skb_vlan_inet_prepare().
The only comment below is about the changelog, so the diff hunks are not
quoted.
[Severity: Low]
Is this description of the call graph accurate?
> __ip6_tnl_rcv() is reached through ip6_tnl_rcv() from both ip6_tunnel
> (ip4ip6, ip6ip6) and ip6_gre (ip6gre, ip6gretap, erspan).
In net/ipv6/ip6_tunnel.c, the exported ip6_tnl_rcv() only has callers in
net/ipv6/ip6_gre.c (the ip6gre_rcv() and ip6erspan_rcv() paths). The
ip6_tunnel-native encapsulations do not go through it; they call
__ip6_tnl_rcv() directly from the static ipxip6_rcv():
net/ipv6/ip6_tunnel.c:ipxip6_rcv() {
...
ret = __ip6_tnl_rcv(t, skb, tpi, tun_dst, dscp_ecn_decapsulate,
log_ecn_error);
...
}
with ip4ip6_rcv()->ipxip6_rcv(), ip6ip6_rcv()->ipxip6_rcv() and
mplsip6_rcv()->ipxip6_rcv().
That also makes mplsip6 a third ip6_tunnel encapsulation that starts
reporting these reasons, which the changelog does not mention.
The conclusion drawn afterwards does still hold, since tpi_v4, tpi_v6 and
tpi_mpls are static descriptors with only .proto set:
net/ipv6/ip6_tunnel.c
static const struct tnl_ptk_info tpi_mpls = {
/* no tunnel info required for mplsip6. */
.proto = htons(ETH_P_MPLS_UC),
};
so no checksum or sequence bit is ever set on the ipxip6 path. Could the
entry point description be adjusted to name ipxip6_rcv() and include
mplsip6?
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260913034937.875068-1-littlesmilingcloud%40gmail.com
next prev parent reply other threads:[~2026-09-14 4:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 3:49 [PATCH net-next v2 0/8] tunnels: add core and gre drop reasons Anton Danilov
2026-09-13 3:49 ` [PATCH net-next v2 1/8] ip_tunnel: add drop reasons to the generic RX path Anton Danilov
2026-09-13 3:49 ` [PATCH net-next v2 2/8] ip6_tunnel: " Anton Danilov
2026-09-14 4:37 ` netdev-bot+sashiko [this message]
2026-09-13 3:49 ` [PATCH net-next v2 3/8] gre: make gre_parse_header() report a drop reason Anton Danilov
2026-09-14 4:37 ` netdev-bot+sashiko
2026-09-13 3:49 ` [PATCH net-next v2 4/8] ip_gre: add drop reasons to the RX path Anton Danilov
2026-09-14 4:37 ` netdev-bot+sashiko
2026-09-13 3:49 ` [PATCH net-next v2 5/8] ip6_gre: " Anton Danilov
2026-09-13 3:49 ` [PATCH net-next v2 6/8] ip_tunnel: add drop reasons to the transmit path Anton Danilov
2026-09-13 3:49 ` [PATCH net-next v2 7/8] ip_gre: " Anton Danilov
2026-09-13 3:49 ` [PATCH net-next v2 8/8] ip6_tunnel: " Anton Danilov
2026-09-14 4:37 ` netdev-bot+sashiko
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=178936063923.22033.2072645913150981969@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--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.