From: Pablo Neira Ayuso <pablo@netfilter.org>
To: John <shffr@protonmail.com>
Cc: "netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
"coreteam@netfilter.org" <coreteam@netfilter.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] netfilter: flowtable: XMIT_NEIGH flows sent to 00:00:00:00:00:00 once the next hop's neighbour entry is gone
Date: Fri, 20 Nov 2026 01:16:54 +0100 [thread overview]
Message-ID: <av-RdjXsq4IXsnMg@chamomile> (raw)
In-Reply-To: <LCJrB-Fde--T9NiYx2QfFb-X-9W-vsYYmtmrHwIKuKgM8enKRWF2DYypz2_zJKSKQBMUdb9sS6xMEfPihv1YO2FLjX1OUN-Td3Hq1eAdLgw=@protonmail.com>
On Thu, Nov 12, 2026 at 09:08:27AM +0000, John wrote:
> Hi Pablo, Thorsten,
>
> Thorsten: I first saw this on 6.18.60 and have reproduced it on
> 6.18.62 and v7.4-rc2. 6.18.63 has the same nf_flow_table_ip.c.
> b5964aac51e0 came into 6.18.y with 6.18.45, the release named in
> the thread you linked.
>
> Pablo: on 7.4-rc2 your patch stops the black hole, but as you
> noticed, one packet is still lost each time the next hop's entry
> goes away, which with neighbour GC happens about every 75 s on a
> long-lived flow. 6.18.44, before b5964aac51e0, lost nothing in
> the same tests. On 6.18.y the patch only works together with
> 871df5007eda.
For the record, I posted these series to address this issue:
https://lore.kernel.org/netfilter-devel/20261119090736.3342541-1-pablo@netfilter.org/T/
next prev parent reply other threads:[~2026-11-20 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 21:26 [REGRESSION] netfilter: flowtable: XMIT_NEIGH flows sent to 00:00:00:00:00:00 once the next hop's neighbour entry is gone John
2026-11-11 8:49 ` Thorsten Leemhuis
2026-11-11 15:21 ` Pablo Neira Ayuso
2026-11-11 22:09 ` Pablo Neira Ayuso
2026-11-12 9:08 ` John
2026-11-20 0:16 ` Pablo Neira Ayuso [this message]
2026-11-17 1:20 ` 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=av-RdjXsq4IXsnMg@chamomile \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=regressions@lists.linux.dev \
--cc=shffr@protonmail.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