Re: [PATCH 6.1.y 6.6.y] netfilter: nft_set_pipapo: restore cloned mapping table memcg accounting

Pablo Neira Ayuso <[email protected]>
Newsgroups gmane.comp.security.firewalls.netfilter.devel,gmane.linux.kernel.stable,gmane.linux.network,gmane.linux.kernel
Message-ID <apitu8BYUvG-WJt2@chamomile>
On Wed, Sep 02, 2026 at 06:14:13PM -0400, Sasha Levin wrote:
> > Fixes: a4983e89e3b1 ("netfilter: nft_set_pipapo: do not rely on ZERO_SIZE_PTR")
> > Fixes: 32bad10de347 ("netfilter: nft_set_pipapo: do not rely on ZERO_SIZE_PTR")
> >
> > This two Fixes: tag do not make any sense to me.
> 
> > The two Fixes tags are for the two stable branches:
> >
> > - a4983e89e3b1 is the 6.1.y backport
> > - 32bad10de347 is the 6.6.y backport
> >
> > I am not sure what the usual preference is here: one common patch with
> > both Fixes tags, or separate patches for each tree. Which do you prefer?
> 
> Whatever Pablo prefers :)

I am fine either way. I just got confused with the double Fixes: tag
that point to the -stable tree commit hash (if I understood correctly
after Karl's explaination).
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.