APPLIED/Cmnt: [SRU][Noble][PULL] Noble upstream stable patchset 2026-06-08

[Alice C. Munduruca]

On Tue, 29 Sept 2026 at 06:06, Nicolas Dichtel
<nicolas.dichtel at 6wind.com> wrote:
>
> Hello Alice,
>
> Le 28/09/2026 à 17:41, Alice C. Munduruca a écrit :
> [snip]
>
> >>>> Pablo Neira Ayuso (7):
> >>>>        netfilter: flowtable: strictly check for maximum number of actions
> >>>>        netfilter: nf_conntrack_expect: honor expectation helper field
> >> This commit ...
> >>
> >>>>        netfilter: nf_conntrack_expect: use expect->helper
> >>>>        netfilter: nf_conntrack_expect: store netns and zone in expectation
> >>>>        netfilter: ctnetlink: ignore explicit helper on new expectations
> >> ... and this one have introduced a regression.
> >>
> >> It has been fixed upstream in v7.1 in commit dcb0f9aefdd6 ("netfilter:
> >> nf_conntrack_expect: restore helper propagation via expectation").
> >
> > This commit has landed in upstream stable branches we track for these
> > upstream stable patchsets. Some time this/next week, we will release a
> > patchset containing changes from v6.6.151 and v6.12.103, both of which
> > contain backports of this fix.
> >
> > Once that patchset is applied, you will be able to test the kernel
> > built with its changes a week later, available in -proposed. [1] After
> > two weeks it will be released at large. [2]
> >
>
> Thanks for the quick reply and the details.
> I took a quick look at the "noble" git tree, but I didn't find the fix there. Is
> it publicly visible somewhere?

Not yet. As far as I know, the patchset has been prepared locally, but
has not yet been pushed to the upstream stable git repository for
noble. [3] It will drop there before it migrates to the official noble
repository.

That migration will only happen after the corresponding upstream
stable update pull request appears on this mailing list (with "Ported
from the following upstream stable releases: v6.6.151, v6.12.103") and
is applied by the SRU Cycle Lead.

At that point the timeline I pointed to above goes into effect.
Currently, we expect the patchset with your fix to be applied before
next Wednesday, although there is no guarantee.

>
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dcb0f9aefdd6
> >>
> >> Should I open a launchpad entry to request a backport to the noble (6.8) kernel?
> >
> > No launchpad bug is thus necessary, although thanks for letting us know :)
>
> Regards,
> Nicolas

Hopefully this helps to clarify my previous message!
 - Alice C. Munduruca

[3]: https://launchpad.net/~ubuntu-kernel-stable/+git/noble