From: Ritaro Takenaka <ritarot634@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Ritaro Takenaka <ritarot634@gmail.com>
Subject: [PATCH] nf_flowtable: ensure dst.dev is not blackhole
Date: Mon, 25 Apr 2022 17:08:38 +0900 [thread overview]
Message-ID: <20220425080835.5765-1-ritarot634@gmail.com> (raw)
Fixes sporadic IPv6 packet loss when flow offloading is enabled.
IPv6 route GC calls dst_dev_put() which makes dst.dev blackhole_netdev
even if dst is cached in flow offload. If a packet passes through this
invalid flow, packet loss will occur.
This is from Commit 227e1e4d0d6c (netfilter: nf_flowtable: skip device
lookup from interface index), as outdev was cached independently before.
Packet loss is reported on OpenWrt with Linux 5.4 and later.
Signed-off-by: Ritaro Takenaka <ritarot634@gmail.com>
---
net/netfilter/nf_flow_table_ip.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/net/netfilter/nf_flow_table_ip.c b/net/netfilter/nf_flow_table_ip.c
index 32c0eb1b4..12f81661d 100644
--- a/net/netfilter/nf_flow_table_ip.c
+++ b/net/netfilter/nf_flow_table_ip.c
@@ -624,6 +624,11 @@ nf_flow_offload_ipv6_hook(void *priv, struct sk_buff *skb,
if (nf_flow_state_check(flow, ip6h->nexthdr, skb, thoff))
return NF_ACCEPT;
+ if (unlikely(tuplehash->tuple.dst_cache->dev == blackhole_netdev)) {
+ flow_offload_teardown(flow);
+ return NF_ACCEPT;
+ }
+
if (skb_try_make_writable(skb, thoff + hdrsize))
return NF_DROP;
--
2.25.1
next reply other threads:[~2022-04-25 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 8:08 Ritaro Takenaka [this message]
2022-04-26 11:21 ` [PATCH] nf_flowtable: ensure dst.dev is not blackhole Pablo Neira Ayuso
2022-04-26 11:55 ` りたろう
2022-04-26 12:28 ` Ritaro Takenaka
2022-04-27 15:10 ` Pablo Neira Ayuso
2022-04-30 17:23 ` Ritaro Takenaka
2022-05-09 6:32 ` Pablo Neira Ayuso
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=20220425080835.5765-1-ritarot634@gmail.com \
--to=ritarot634@gmail.com \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).