From: Karl Mehltretter <kmehltretter@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: stable@vger.kernel.org, Florian Westphal <fw@strlen.de>,
Phil Sutter <phil@nwl.cc>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Mukul Sikka <mukul.sikka@broadcom.com>,
Keerthana K <keerthana.kalyanasundaram@broadcom.com>,
Stefano Brivio <sbrivio@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Brennan Lamoreaux <brennan.lamoreaux@broadcom.com>,
Bin Lan <lanbincn@139.com>, XiaoHua Wang <561399680@139.com>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1.y 6.6.y] netfilter: nft_set_pipapo: restore cloned mapping table memcg accounting
Date: Tue, 1 Sep 2026 01:15:33 +0200 [thread overview]
Message-ID: <apYKQbvpIWvY8Jqi@gmail.com> (raw)
In-Reply-To: <apX9AZoNkpVrBMIE@chamomile>
On Tue, Sep 01, 2026 at 12:15:29AM +0100, Pablo Neira Ayuso 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
Both backports changed this allocation from GFP_KERNEL_ACCOUNT back to
GFP_KERNEL, which introduced the regression. The accounting was correct
before these commits.
I used one Fixes tag for each target tree. 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?
Thanks,
Karl
next prev parent reply other threads:[~2026-08-31 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 19:49 [PATCH 6.1.y 6.6.y] netfilter: nft_set_pipapo: restore cloned mapping table memcg accounting Karl Mehltretter
2026-08-31 22:15 ` Pablo Neira Ayuso
2026-08-31 23:15 ` Karl Mehltretter [this message]
2026-09-02 22:14 ` Sasha Levin
2026-09-02 23:14 ` Pablo Neira Ayuso
2026-09-03 0:01 ` Karl Mehltretter
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=apYKQbvpIWvY8Jqi@gmail.com \
--to=kmehltretter@gmail.com \
--cc=561399680@139.com \
--cc=brennan.lamoreaux@broadcom.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=keerthana.kalyanasundaram@broadcom.com \
--cc=kuba@kernel.org \
--cc=lanbincn@139.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukul.sikka@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=sbrivio@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.