public inbox for netfilter-devel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH 2/5] cache: Respect family in all list commands
Date: Wed, 11 Mar 2026 13:11:56 +0100	[thread overview]
Message-ID: <abFcDNwnKzer7_r7@chamomile> (raw)
In-Reply-To: <abFBziaYqOenTfVt@orbyte.nwl.cc>

On Wed, Mar 11, 2026 at 11:19:58AM +0100, Phil Sutter wrote:
> On Wed, Mar 11, 2026 at 10:34:59AM +0100, Pablo Neira Ayuso wrote:
> > On Wed, Mar 11, 2026 at 12:11:12AM +0100, Phil Sutter wrote:
> > > Some list commands did not set filter->list.family even if one was given
> > > on command line, fix this.
> > > 
> > 
> > Fixes: a1a6b0a5c3c4 ("cache: finer grain cache population for list commands")
> 
> Hmm. At that point, we didn't have 'filter' parameter in
> evaluate_cache_list(). Struct nft_cache_filter was introduced later, in
> commit 3f1d3912c3a6b ("cache: filter out tables that are not
> requested").
> 
> Assuming that Fixes: tags are used for semi-automated backporting (at
> least I do ;), pointing at that commit will cause trouble.

Good point.

Helping identify backporting in a semi-automated way is good,
specially for small fixes like this.

At least for me, it helps me identify if it is an
update/enhancement/feature or fix, it is just a bit more context
information.

> Do you still think we should add that tag?

I get your point that tags need to be right if we use them.

  reply	other threads:[~2026-03-11 12:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 23:11 [nft PATCH 0/5] Enhance cache filter for list commands Phil Sutter
2026-03-10 23:11 ` [nft PATCH 1/5] cache: Include chains, flowtables and objects in netlink debug output Phil Sutter
2026-03-10 23:11 ` [nft PATCH 2/5] cache: Respect family in all list commands Phil Sutter
2026-03-11  9:34   ` Pablo Neira Ayuso
2026-03-11 10:19     ` Phil Sutter
2026-03-11 12:11       ` Pablo Neira Ayuso [this message]
2026-03-11 14:01         ` Phil Sutter
2026-03-10 23:11 ` [nft PATCH 3/5] cache: Relax chain_cache_dump filter application Phil Sutter
2026-03-11  9:38   ` Pablo Neira Ayuso
2026-03-10 23:11 ` [nft PATCH 4/5] cache: Filter for table when listing sets or maps Phil Sutter
2026-03-11  9:39   ` Pablo Neira Ayuso
2026-03-10 23:11 ` [nft PATCH 5/5] cache: Filter for table when listing flowtables Phil Sutter
2026-03-11  9:40   ` Pablo Neira Ayuso
2026-03-11 15:06 ` [nft PATCH 0/5] Enhance cache filter for list commands Eric Garver
2026-03-11 19:15   ` Phil Sutter
2026-03-18 16:23 ` Phil Sutter
2026-03-18 16:58   ` Pablo Neira Ayuso
2026-03-18 16:59     ` Pablo Neira Ayuso
2026-03-18 18:49       ` Phil Sutter

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=abFcDNwnKzer7_r7@chamomile \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=phil@nwl.cc \
    /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