From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, chzhengyang2023@lzu.edu.cn
Subject: Re: [PATCH nf 3/3] netfilter: flowtable: support IPIP tunnel with direct xmit
Date: Mon, 29 Jun 2026 17:13:52 +0200 [thread overview]
Message-ID: <akKLsIf-NSC75B1Q@lore-desk> (raw)
In-Reply-To: <20260629143936.61239-4-pablo@netfilter.org>
[-- Attachment #1: Type: text/plain, Size: 4498 bytes --]
On Jun 29, Pablo Neira Ayuso wrote:
> The combination of IPIP tunnel with direct xmit, eg. bridge device,
> breaks because no dst_entry is provided to check the skb headroom and to
> set the iph->frag_off field. This leads to invalid dst usage and can
> trigger a crash in the tunnel transmit path.
>
> Fix this by moving dst_cache and dst_cookie out of the runtime union so
> that they can be shared by neighbour, xfrm, and direct tunnel flows.
> For FLOW_OFFLOAD_XMIT_DIRECT tuples carrying tunnel metadata, preserve
> route state in these shared fields and release it through the common
> dst release path.
>
> Since dst_entry is now available to the three supported xmit modes and
> dst_release() already deals with NULL dst, remove the xmit type check
> in nft_flow_dst_release(). Moreover, skip the check if the dst entry
> is NULL in nf_flow_dst_check() which is now the case for the direct
> xmit case.
>
> Based on patch from Rein Wei <n05ec@lzu.edu.cn>.
>
> Fixes: d30301ba4b07 ("netfilter: flowtable: Add IPIP tx sw acceleration")
> Reported-by: Yuan Tan <yuantan098@gmail.com>
> Reported-by: Xin Liu <bird@lzu.edu.cn>
> Reported-by: Zhengyang Chen <chzhengyang2023@lzu.edu.cn>
> Reported-by: Ren Wei <n05ec@lzu.edu.cn>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> include/net/netfilter/nf_flow_table.h | 4 ++--
> net/netfilter/nf_flow_table_core.c | 15 +++++++++++----
> net/netfilter/nf_flow_table_ip.c | 3 +--
> 3 files changed, 14 insertions(+), 8 deletions(-)
>
> diff --git a/include/net/netfilter/nf_flow_table.h b/include/net/netfilter/nf_flow_table.h
> index 7b23b245a5a8..369f6a717811 100644
> --- a/include/net/netfilter/nf_flow_table.h
> +++ b/include/net/netfilter/nf_flow_table.h
> @@ -155,11 +155,11 @@ struct flow_offload_tuple {
> tun_num:2,
> in_vlan_ingress:2;
> u16 mtu;
> + struct dst_entry *dst_cache;
> + u32 dst_cookie;
nit: if you swap dst_cache and dst_cookie we can avoid a 4 bytes padding hole.
> union {
> struct {
> - struct dst_entry *dst_cache;
> u32 ifidx;
> - u32 dst_cookie;
> };
> struct {
> u32 ifidx;
> diff --git a/net/netfilter/nf_flow_table_core.c b/net/netfilter/nf_flow_table_core.c
> index 99c5b9d671a0..6f195ccf222a 100644
> --- a/net/netfilter/nf_flow_table_core.c
> +++ b/net/netfilter/nf_flow_table_core.c
> @@ -127,12 +127,21 @@ static int flow_offload_fill_route(struct flow_offload *flow,
>
> switch (route->tuple[dir].xmit_type) {
> case FLOW_OFFLOAD_XMIT_DIRECT:
> + if (flow_tuple->tun_num) {
> + flow_tuple->dst_cache = dst;
> + flow_tuple->dst_cookie =
> + flow_offload_dst_cookie(flow_tuple);
> + } else {
> + flow_tuple->dst_cache = NULL;
> + flow_tuple->dst_cookie = 0;
nit: since we use kmem_cache_zalloc() in flow_offload_alloc() do we need the else
branch?
> + }
> memcpy(flow_tuple->out.h_dest, route->tuple[dir].out.h_dest,
> ETH_ALEN);
> memcpy(flow_tuple->out.h_source, route->tuple[dir].out.h_source,
> ETH_ALEN);
> flow_tuple->out.ifidx = route->tuple[dir].out.ifindex;
> - dst_release(dst);
> + if (!flow_tuple->tun_num)
> + dst_release(dst);
> break;
> case FLOW_OFFLOAD_XMIT_XFRM:
> case FLOW_OFFLOAD_XMIT_NEIGH:
> @@ -152,9 +161,7 @@ static int flow_offload_fill_route(struct flow_offload *flow,
> static void nft_flow_dst_release(struct flow_offload *flow,
> enum flow_offload_tuple_dir dir)
> {
> - if (flow->tuplehash[dir].tuple.xmit_type == FLOW_OFFLOAD_XMIT_NEIGH ||
> - flow->tuplehash[dir].tuple.xmit_type == FLOW_OFFLOAD_XMIT_XFRM)
> - dst_release(flow->tuplehash[dir].tuple.dst_cache);
> + dst_release(flow->tuplehash[dir].tuple.dst_cache);
> }
>
> void flow_offload_route_init(struct flow_offload *flow,
> diff --git a/net/netfilter/nf_flow_table_ip.c b/net/netfilter/nf_flow_table_ip.c
> index 089f2bc19972..0b78decce8a9 100644
> --- a/net/netfilter/nf_flow_table_ip.c
> +++ b/net/netfilter/nf_flow_table_ip.c
> @@ -299,8 +299,7 @@ static bool nf_flow_exceeds_mtu(const struct sk_buff *skb, unsigned int mtu)
>
> static inline bool nf_flow_dst_check(struct flow_offload_tuple *tuple)
> {
> - if (tuple->xmit_type != FLOW_OFFLOAD_XMIT_NEIGH &&
> - tuple->xmit_type != FLOW_OFFLOAD_XMIT_XFRM)
> + if (!tuple->dst_cache)
> return true;
>
> return dst_check(tuple->dst_cache, tuple->dst_cookie);
> --
> 2.47.3
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-06-29 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 14:39 [PATCH nf 0/3] flowtable fixes for ipip tunnels Pablo Neira Ayuso
2026-06-29 14:39 ` [PATCH nf 1/3] netfilter: flowtable: use dst in this direction when pushing IPIP header Pablo Neira Ayuso
2026-06-29 15:17 ` Lorenzo Bianconi
2026-06-29 14:39 ` [PATCH nf 2/3] netfilter: flowtable: IPIP tunnel hardware offload is not yet support Pablo Neira Ayuso
2026-06-29 15:15 ` Lorenzo Bianconi
2026-06-29 14:39 ` [PATCH nf 3/3] netfilter: flowtable: support IPIP tunnel with direct xmit Pablo Neira Ayuso
2026-06-29 15:13 ` Lorenzo Bianconi [this message]
2026-07-01 6:44 ` [PATCH nf 0/3] flowtable fixes for ipip tunnels 陈正阳
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=akKLsIf-NSC75B1Q@lore-desk \
--to=lorenzo@kernel.org \
--cc=chzhengyang2023@lzu.edu.cn \
--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