Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4;
Date:   Mon, 16 Oct 2023 07:20:06 +0700
From:   Bagas Sanjaya <bagasdotme@gmail.com>
To:     Vladimir Smelhaus <vl.sm@email.cz>,
        Linux Netfilter <netfilter@vger.kernel.org>,
        coreteam@netfilter.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Regressions <regressions@lists.linux.dev>
Cc:     Pablo Neira Ayuso <pablo@netfilter.org>,
        Jozsef Kadlecsik <kadlec@netfilter.org>,
        Florian Westphal <fw@strlen.de>
Subject: Re: Flowtables ignore timeout settings in recent kernels
Message-ID: <ZSyBtn8cplLWoNn-@debian.me>
References: <ughg4v$130b$1@ciao.gmane.io>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="N2rAuLPZGqdFV0iZ"
Content-Disposition: inline
In-Reply-To: <ughg4v$130b$1@ciao.gmane.io>
Precedence: bulk


--N2rAuLPZGqdFV0iZ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Oct 15, 2023 at 09:56:14PM +0200, Vladimir Smelhaus wrote:
> Netfilter ignores the timeout settings for a flowtable
>=20
> # sysctl -a -r flowtable
> net.netfilter.nf_flowtable_tcp_timeout =3D 30
> net.netfilter.nf_flowtable_udp_timeout =3D 30
>=20
> Situation. A long udp connection (tunnel) with some data flowing through a
> router. The connection is sent to a flowtable on the router. It's a few
> packets per second, more here and there, a pause here and there, and so on
> over and over. The pauses are minimal and are also limited by the tunnel
> settings to be no longer than 25 seconds. Everything is satisfying to make
> the connection last continuously in the flowtable and not reappear in
> forward. However, the connection keeps dropping out of the flowtable. It
> stays in the flowtable (offloaded) for a second at most and then it is
> kicked out, back to forward.
>=20
> In an attached test script you can see counters that should be zero but a=
re not. If I watch the normal packet flow on a particular router, I can see=
 packets in the conntrack table that should be OFFLOAD as ASSURED.
>=20
> Tested in kernel 6.5.6. In an old(er) kernel 5.10 it works as expected.
>=20

Then please perform bisection to find a culprit that introduces your
regression (see Documentation/admin-guide/bug-bisect.rst in the kernel
sources for reference). Also, it'd been great if you also post the
reproducer script inline (within your email) instead, as some MUAs
(like mutt that I'm using now) may ignore the attachment.

Anyway, thanks for the regression report. I'm adding it to regzbot:

#regzbot ^introduced: v5.10..v6.5

--=20
An old man doll... just what I always wanted! - Clara

--N2rAuLPZGqdFV0iZ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZSyBsAAKCRD2uYlJVVFO
oxD9AQDAp/pXr+d44wTxEyg9copCJnaEVKIixfFsamXwbWpI/QD/W2ZAb9J8yPcv
V/en2pgBB1CgZDhm7JzlxcWUrsKROwM=
=u4d8
-----END PGP SIGNATURE-----

--N2rAuLPZGqdFV0iZ--