From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: stable@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Subject: Re: network flow offloading broken in 6.18.45+
Date: Mon, 14 Sep 2026 14:36:16 +0200 [thread overview]
Message-ID: <aqfqQPP2Y7iG3kM_@chamomile> (raw)
In-Reply-To: <aqfofgtUfyXlfHLr@chamomile>
On Mon, Sep 14, 2026 at 02:28:49PM +0200, Pablo Neira Ayuso wrote:
> Hi,
>
> On Mon, Sep 14, 2026 at 12:13:50AM +0200, Pablo Neira Ayuso wrote:
> > On Mon, Sep 14, 2026 at 12:12:16AM +0200, Pablo Neira Ayuso wrote:
> > > Hi Hauke,
> > >
> > > On Wed, Sep 09, 2026 at 06:29:50PM +0200, Hauke Mehrtens wrote:
> > > > Hi,
> > > >
> > > > flow offloading is currently broken in Linux 6.18.45.
> > > >
> > > > Since the backport of commit b5964aac51e0 ("netfilter: flowtable:
> > > > consolidate xmit path") to Linux 6.18.45. This is happening in a router with
> > > > traffic from wifi to the Ethernet device when mac80211 returns -EOPNOTSUPP.
> > > >
> > > > Upstream fixed it in 871df5007eda ("netfilter: flowtable: bail out if
> > > > forward path cannot be discovered") by not offloading the flow at all.
> > > > backporting this change looks more complicated.
> > > >
> > > > This cam up in a discussion in an OpenWrt PR:
> > > > https://github.com/openwrt/openwrt/pull/24800
> > > >
> > > > An LLM suggested this change: https://github.com/openwrt/openwrt/pull/24800/changes/394d741e6e76ecd172dbbf1d9ba171e378211734
> > >
> > > Patch went away.
> > >
> > > > It seams to work, but I do not understand this part of the code god enough
> > > > to judge if this is correct.
> > >
> > > Could you attach the patch to this email for review?
> >
> > I've found it :)
> >
> > https://github.com/openwrt/openwrt/commit/d2b53b8043e17087b877bfc2335cbba87dffb4e0
>
> I've proposed the following fix:
>
> https://lore.kernel.org/netfilter-devel/20260914122456.1963453-1-pablo@netfilter.org/
Actually, this v2 should work:
https://lore.kernel.org/netfilter-devel/20260914123334.1964397-1-pablo@netfilter.org/
next prev parent reply other threads:[~2026-09-14 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 16:29 network flow offloading broken in 6.18.45+ Hauke Mehrtens
2026-09-13 22:12 ` Pablo Neira Ayuso
2026-09-13 22:13 ` Pablo Neira Ayuso
2026-09-14 12:28 ` Pablo Neira Ayuso
2026-09-14 12:36 ` Pablo Neira Ayuso [this message]
2026-09-15 0:20 ` Hauke Mehrtens
2026-09-15 8:15 ` Pablo Neira Ayuso
2026-09-16 19:28 ` Sasha Levin
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=aqfqQPP2Y7iG3kM_@chamomile \
--to=pablo@netfilter.org \
--cc=hauke@hauke-m.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=stable@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