From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: stable@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: Backport request: "netfilter: nf_conntrack_expect: restore helper propagation via expectation"
Date: Thu, 30 Jul 2026 01:07:39 +0200 [thread overview]
Message-ID: <amqHu5H6xu02Izo8@chamomile> (raw)
In-Reply-To: <ee95f6ac-181e-4315-a2ae-e4d1388c5e69@ovn.org>
On Wed, Jul 29, 2026 at 11:38:17PM +0200, Ilya Maximets wrote:
> Hi. The mentioned commit dcb0f9aefdd604d36710fda53c25bd7cf4a3e37a
> was backported to 7.0, but not further, while two commits it is fixing
> were backported down to 6.1.
>
> Admittedly, the patch is not very important as far as functionality
> goes (at least for FTP), but the issue does change the user visible
> behavior and that makes all the FTP system tests in openvswitch
> project (in userspace) to fail. This makes it harder to validate OVS
> on kernels below 7.0 and makes it unnecessarily harder to validate
> changes for the openvswitch kernel module on stable kernels.
>
> So, it would be really nice to have the fix backported to the same
> branches where the commits it fixes were (6.1).
>
> AFAICT, cherry-pick works without conflicts down to 6.6. For 6.1
> there is a minor conflict, 6.1.y has the extra debug message:
>
> diff --cc net/netfilter/nf_conntrack_core.c
> index f5c466ea1e7d,8ba5b22a1eef..000000000000
> --- a/net/netfilter/nf_conntrack_core.c
> +++ b/net/netfilter/nf_conntrack_core.c
> @@@ -1800,8 -1811,8 +1800,10 @@@ init_conntrack(struct net *net, struct
> spin_lock_bh(&nf_conntrack_expect_lock);
> exp = nf_ct_find_expectation(net, zone, tuple, !tmpl || nf_ct_is_confirmed(tmpl));
> if (exp) {
> + struct nf_conntrack_helper *assign_helper;
> +
> + pr_debug("expectation arrives ct=%p exp=%p\n",
> + ct, exp);
> /* Welcome, Mr. Bond. We've been expecting you... */
> __set_bit(IPS_EXPECTED_BIT, &ct->status);
> /* exp->master safe, refcnt bumped in nf_ct_find_expectation */
> ---
>
> WDYT?
I am fine with getting dcb0f9aefdd604d36710fda53c25bd7cf4a3e37a into
-stable release < 7.0 if that is what you mean.
next prev parent reply other threads:[~2026-07-29 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 21:38 Backport request: "netfilter: nf_conntrack_expect: restore helper propagation via expectation" Ilya Maximets
2026-07-29 23:07 ` Pablo Neira Ayuso [this message]
2026-07-30 14:09 ` Greg KH
2026-07-30 16:26 ` Ilya Maximets
2026-07-31 2:39 ` Sasha Levin
2026-07-30 19:35 ` [PATCH 6.18.y] netfilter: nf_conntrack_expect: restore helper propagation via expectation Ilya Maximets
2026-07-30 19:38 ` [PATCH 6.1.y] " Ilya Maximets
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=amqHu5H6xu02Izo8@chamomile \
--to=pablo@netfilter.org \
--cc=i.maximets@ovn.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