From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Yue Haibing <yuehaibing@huawei.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<horms@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] ipv6: sit: Add ipip6_tunnel_dst_find() for cleanup
Date: Wed, 27 Aug 2025 16:45:22 +0200 [thread overview]
Message-ID: <ec71f1cd-89b9-4a18-bcc6-0bac6f6660d0@intel.com> (raw)
In-Reply-To: <20250827040027.1013335-1-yuehaibing@huawei.com>
From: Yue Haibing <yuehaibing@huawei.com>
Date: Wed, 27 Aug 2025 12:00:27 +0800
> Extract the dst lookup logic from ipip6_tunnel_xmit() into new helper
> ipip6_tunnel_dst_find() to reduce code duplication and enhance readability.
>
> No functional change intended.
...but bloat-o-meter stats would be nice to see here. I'm curious
whether the object code got any changes or the compilers still just
inline this function to both call sites.
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
> ---
> net/ipv6/sit.c | 93 +++++++++++++++++++++++---------------------------
> 1 file changed, 43 insertions(+), 50 deletions(-)
>
> diff --git a/net/ipv6/sit.c b/net/ipv6/sit.c
> index 12496ba1b7d4..bcd261ff985b 100644
> --- a/net/ipv6/sit.c
> +++ b/net/ipv6/sit.c
> @@ -848,6 +848,47 @@ static inline __be32 try_6rd(struct ip_tunnel *tunnel,
> return dst;
> }
>
> +static bool ipip6_tunnel_dst_find(struct sk_buff *skb, __be32 *dst,
> + bool is_isatap)
> +{
> + const struct ipv6hdr *iph6 = ipv6_hdr(skb);
> + struct neighbour *neigh = NULL;
> + const struct in6_addr *addr6;
> + bool found = false;
> + int addr_type;
> +
> + if (skb_dst(skb))
> + neigh = dst_neigh_lookup(skb_dst(skb), &iph6->daddr);
> +
> + if (!neigh) {
> + net_dbg_ratelimited("nexthop == NULL\n");
> + return found;
Return false here right away.
> + }
> +
> + addr6 = (const struct in6_addr *)&neigh->primary_key;
> + addr_type = ipv6_addr_type(addr6);
> +
> + if (is_isatap) {
> + if ((addr_type & IPV6_ADDR_UNICAST) &&
> + ipv6_addr_is_isatap(addr6)) {
> + *dst = addr6->s6_addr32[3];
> + found = true;
> + }
> + } else {
> + if (addr_type == IPV6_ADDR_ANY) {
> + addr6 = &ipv6_hdr(skb)->daddr;
> + addr_type = ipv6_addr_type(addr6);
> + }
> +
> + if ((addr_type & IPV6_ADDR_COMPATv4) != 0) {
> + *dst = addr6->s6_addr32[3];
> + found = true;
> + }
> + }
> + neigh_release(neigh);
> + return found;
I'd put 2 additional newlines here:
}
neigh_release(neigh);
return found;
}
for readability purposes and also a NL before the final `return` is
usually mandatory.
Thanks,
Olek
next prev parent reply other threads:[~2025-08-27 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 4:00 Yue Haibing
2025-08-27 14:45 ` Alexander Lobakin [this message]
2025-08-28 6:13 ` Yue Haibing
2025-08-28 6:44 ` Yue Haibing
2025-08-28 15:33 ` Alexander Lobakin
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=ec71f1cd-89b9-4a18-bcc6-0bac6f6660d0@intel.com \
--to=aleksander.lobakin@intel.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuehaibing@huawei.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 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®