From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next 4/4] netfilter: flowtable: release tunnel route on error when building forward path
Date: Sat, 25 Jul 2026 13:05:03 +0200 [thread overview]
Message-ID: <amSYX4uSAaHHJWZR@lore-desk> (raw)
In-Reply-To: <20260723174952.329650-5-pablo@netfilter.org>
[-- Attachment #1: Type: text/plain, Size: 6584 bytes --]
> nft_flow_tunnel_update_route() can lazy fail, leaving an incomplete
> forward path set ip. The route lookup also happens twice, once from
> dev_fill_forward_path() and again in this aforementioned function.
>
> Update ipip and ip6ip6 not to release the dst_entry and pass it on
> via the tunnel forward path information.
>
> In case of failure when setting up the forwarding path, release the
> tunnel dst that was provided via dev_fill_forward_path().
>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Acked-by: Lorenzo Bianconi <lorenzo@kernel.org>
> ---
> net/ipv4/ipip.c | 2 +-
> net/ipv6/ip6_tunnel.c | 2 +-
> net/netfilter/nf_flow_table_path.c | 62 ++++++++----------------------
> 3 files changed, 18 insertions(+), 48 deletions(-)
>
> diff --git a/net/ipv4/ipip.c b/net/ipv4/ipip.c
> index d1aa048a6099..0a4fa1351dd7 100644
> --- a/net/ipv4/ipip.c
> +++ b/net/ipv4/ipip.c
> @@ -370,10 +370,10 @@ static int ipip_fill_forward_path(struct net_device_path_ctx *ctx,
> path->tun.src_v4.s_addr = tiph->saddr;
> path->tun.dst_v4.s_addr = tiph->daddr;
> path->tun.l3_proto = IPPROTO_IPIP;
> + path->tun.dst = &rt->dst;
> path->dev = ctx->dev;
>
> ctx->dev = rt->dst.dev;
> - ip_rt_put(rt);
>
> return 0;
> }
> diff --git a/net/ipv6/ip6_tunnel.c b/net/ipv6/ip6_tunnel.c
> index bf8e40af60b0..312de4a6e160 100644
> --- a/net/ipv6/ip6_tunnel.c
> +++ b/net/ipv6/ip6_tunnel.c
> @@ -1864,12 +1864,12 @@ static int ip6_tnl_fill_forward_path(struct net_device_path_ctx *ctx,
> path->tun.src_v6 = t->parms.laddr;
> path->tun.dst_v6 = t->parms.raddr;
> path->tun.l3_proto = IPPROTO_IPV6;
> + path->tun.dst = dst;
> path->dev = ctx->dev;
> ctx->dev = dst->dev;
> }
>
> err = dst->error;
> - dst_release(dst);
>
> return err;
> }
> diff --git a/net/netfilter/nf_flow_table_path.c b/net/netfilter/nf_flow_table_path.c
> index 8f04a4487897..9f6fc29c4e16 100644
> --- a/net/netfilter/nf_flow_table_path.c
> +++ b/net/netfilter/nf_flow_table_path.c
> @@ -82,6 +82,7 @@ struct nft_forward_info {
> } encap[NF_FLOW_TABLE_ENCAP_MAX];
> u8 num_encaps;
> struct flow_offload_tunnel tun;
> + struct dst_entry *tun_dst;
> u8 num_tuns;
> u8 ingress_vlans;
> u8 h_source[ETH_ALEN];
> @@ -124,15 +125,16 @@ static int nft_dev_path_info(const struct net_device_path_stack *stack,
> /* DEV_PATH_VLAN, DEV_PATH_PPPOE and DEV_PATH_TUN */
> if (path->type == DEV_PATH_TUN) {
> if (info->num_tuns)
> - return -1;
> + goto err_out;
>
> info->tun.src_v6 = path->tun.src_v6;
> info->tun.dst_v6 = path->tun.dst_v6;
> info->tun.l3_proto = path->tun.l3_proto;
> + info->tun_dst = path->tun.dst;
> info->num_tuns++;
> } else {
> if (info->num_encaps >= NF_FLOW_TABLE_ENCAP_MAX)
> - return -1;
> + goto err_out;
>
> info->encap[info->num_encaps].id =
> path->encap.id;
> @@ -153,13 +155,13 @@ static int nft_dev_path_info(const struct net_device_path_stack *stack,
> switch (path->bridge.vlan_mode) {
> case DEV_PATH_BR_VLAN_UNTAG_HW:
> if (info->num_encaps == 0)
> - return -1;
> + goto err_out;
>
> info->ingress_vlans |= BIT(info->num_encaps - 1);
> break;
> case DEV_PATH_BR_VLAN_TAG:
> if (info->num_encaps >= NF_FLOW_TABLE_ENCAP_MAX)
> - return -1;
> + goto err_out;
>
> info->encap[info->num_encaps].id = path->bridge.vlan_id;
> info->encap[info->num_encaps].proto = path->bridge.vlan_proto;
> @@ -167,7 +169,7 @@ static int nft_dev_path_info(const struct net_device_path_stack *stack,
> break;
> case DEV_PATH_BR_VLAN_UNTAG:
> if (info->num_encaps == 0)
> - return -1;
> + goto err_out;
>
> info->num_encaps--;
> break;
> @@ -177,7 +179,7 @@ static int nft_dev_path_info(const struct net_device_path_stack *stack,
> info->xmit_type = FLOW_OFFLOAD_XMIT_DIRECT;
> break;
> default:
> - return -1;
> + goto err_out;
> }
> }
>
> @@ -189,6 +191,11 @@ static int nft_dev_path_info(const struct net_device_path_stack *stack,
> return -1;
>
> return 0;
> +err_out:
> + if (info->num_tuns)
> + dst_release(info->tun_dst);
> +
> + return -1;
> }
>
> static bool nft_flowtable_find_dev(const struct net_device *dev,
> @@ -208,44 +215,6 @@ static bool nft_flowtable_find_dev(const struct net_device *dev,
> return found;
> }
>
> -static int nft_flow_tunnel_update_route(const struct nft_pktinfo *pkt,
> - struct flow_offload_tunnel *tun,
> - struct nf_flow_route *route,
> - enum ip_conntrack_dir dir)
> -{
> - struct dst_entry *cur_dst = route->tuple[dir].dst;
> - struct dst_entry *tun_dst = NULL;
> - struct flowi fl = {};
> -
> - switch (nft_pf(pkt)) {
> - case NFPROTO_IPV4:
> - fl.u.ip4.daddr = tun->dst_v4.s_addr;
> - fl.u.ip4.saddr = tun->src_v4.s_addr;
> - fl.u.ip4.flowi4_iif = nft_in(pkt)->ifindex;
> - fl.u.ip4.flowi4_dscp = ip4h_dscp(ip_hdr(pkt->skb));
> - fl.u.ip4.flowi4_mark = pkt->skb->mark;
> - fl.u.ip4.flowi4_flags = FLOWI_FLAG_ANYSRC;
> - break;
> - case NFPROTO_IPV6:
> - fl.u.ip6.daddr = tun->dst_v6;
> - fl.u.ip6.saddr = tun->src_v6;
> - fl.u.ip6.flowi6_iif = nft_in(pkt)->ifindex;
> - fl.u.ip6.flowlabel = ip6_flowinfo(ipv6_hdr(pkt->skb));
> - fl.u.ip6.flowi6_mark = pkt->skb->mark;
> - fl.u.ip6.flowi6_flags = FLOWI_FLAG_ANYSRC;
> - break;
> - }
> -
> - nf_route(nft_net(pkt), &tun_dst, &fl, false, nft_pf(pkt));
> - if (!tun_dst)
> - return -ENOENT;
> -
> - route->tuple[dir].dst = tun_dst;
> - dst_release(cur_dst);
> -
> - return 0;
> -}
> -
> static int nft_dev_forward_path(const struct nft_pktinfo *pkt,
> struct nf_flow_route *route,
> const struct nf_conn *ct,
> @@ -270,12 +239,13 @@ static int nft_dev_forward_path(const struct nft_pktinfo *pkt,
> route->tuple[!dir].in.encap[i].proto = info.encap[i].proto;
> }
>
> - if (info.num_tuns &&
> - !nft_flow_tunnel_update_route(pkt, &info.tun, route, dir)) {
> + if (info.num_tuns) {
> route->tuple[!dir].in.tun.src_v6 = info.tun.dst_v6;
> route->tuple[!dir].in.tun.dst_v6 = info.tun.src_v6;
> route->tuple[!dir].in.tun.l3_proto = info.tun.l3_proto;
> route->tuple[!dir].in.num_tuns = info.num_tuns;
> + dst_release(route->tuple[dir].dst);
> + route->tuple[dir].dst = info.tun_dst;
> }
>
> route->tuple[!dir].in.num_encaps = info.num_encaps;
> --
> 2.47.3
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-07-25 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 17:49 [PATCH nf-next 0/4] flowtable: pass dst_entry from ipip tunnel Pablo Neira Ayuso
2026-07-23 17:49 ` [PATCH nf-next 1/4] netfilter: flowtable: consolidate net_device field in nft_forward_info struct Pablo Neira Ayuso
2026-07-25 10:20 ` Lorenzo Bianconi
2026-07-23 17:49 ` [PATCH nf-next 2/4] netfilter: flowtable: consolidate flowtable device check Pablo Neira Ayuso
2026-07-25 10:25 ` Lorenzo Bianconi
2026-07-23 17:49 ` [PATCH nf-next 3/4] net: pass dst via net_device_path in dev_fill_forward_path() Pablo Neira Ayuso
2026-07-25 10:56 ` Lorenzo Bianconi
2026-07-23 17:49 ` [PATCH nf-next 4/4] netfilter: flowtable: release tunnel route on error when building forward path Pablo Neira Ayuso
2026-07-25 11:05 ` Lorenzo Bianconi [this message]
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=amSYX4uSAaHHJWZR@lore-desk \
--to=lorenzo@kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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