netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Haller <thaller@redhat.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: NetFilter <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nft 1/1] datatype: explicitly set missing datatypes for TYPE_CT_LABEL,TYPE_CT_EVENTBIT
Date: Tue, 19 Sep 2023 14:30:38 +0200	[thread overview]
Message-ID: <38547bfa61da64801d1cb79f757b40ca1e0c44f4.camel@redhat.com> (raw)
In-Reply-To: <ZQmRoKljTJJWEGx1@calendula>

On Tue, 2023-09-19 at 14:18 +0200, Pablo Neira Ayuso wrote:
> Hi Thomas,
> 
> On Tue, Sep 19, 2023 at 01:28:03PM +0200, Thomas Haller wrote:
> > It's not obvious that two enum values are missing (or why).
> > Explicitly
> > set the values to NULL, so we can see this more easily.
> 
> I think this is uncovering a bug with these selectors.
> 
> When concatenations are used, IIRC the delinerize path needs this.
> 
> TYPE_CT_EVENTBIT does not need this, because this is a statement to
> globally filter ctnetlink events events.
> 
> But TYPE_CT_LABEL is likely not working fine with concatenations.
> 
> Let me take a closer look.

Hi Pablo,

Thank you.

FYI, I have a patch with a unit test that performs some consistency
checks of the "datatypes" array. Only TYPE_CT_LABEL + TYPE_CT_EVENTBIT
are missing.

You don't need to write a test about that. The test is however on top
of  "no recursive make" patches, which I will resent at a later time.


Thomas

> 
> > Signed-off-by: Thomas Haller <thaller@redhat.com>
> > ---
> >  src/datatype.c | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/src/datatype.c b/src/datatype.c
> > index 70c84846f70e..bb0c3cf79150 100644
> > --- a/src/datatype.c
> > +++ b/src/datatype.c
> > @@ -65,6 +65,7 @@ static const struct datatype *datatypes[TYPE_MAX
> > + 1] = {
> >         [TYPE_CT_DIR]           = &ct_dir_type,
> >         [TYPE_CT_STATUS]        = &ct_status_type,
> >         [TYPE_ICMP6_TYPE]       = &icmp6_type_type,
> > +       [TYPE_CT_LABEL]         = NULL,
> >         [TYPE_PKTTYPE]          = &pkttype_type,
> >         [TYPE_ICMP_CODE]        = &icmp_code_type,
> >         [TYPE_ICMPV6_CODE]      = &icmpv6_code_type,
> > @@ -72,8 +73,9 @@ static const struct datatype *datatypes[TYPE_MAX
> > + 1] = {
> >         [TYPE_DEVGROUP]         = &devgroup_type,
> >         [TYPE_DSCP]             = &dscp_type,
> >         [TYPE_ECN]              = &ecn_type,
> > -       [TYPE_FIB_ADDR]         = &fib_addr_type,
> > +       [TYPE_FIB_ADDR]         = &fib_addr_type,
> >         [TYPE_BOOLEAN]          = &boolean_type,
> > +       [TYPE_CT_EVENTBIT]      = NULL,
> >         [TYPE_IFNAME]           = &ifname_type,
> >         [TYPE_IGMP_TYPE]        = &igmp_type_type,
> >         [TYPE_TIME_DATE]        = &date_type,
> > -- 
> > 2.41.0
> > 
> 


  reply	other threads:[~2023-09-19 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 11:28 [PATCH nft 1/1] datatype: explicitly set missing datatypes for TYPE_CT_LABEL,TYPE_CT_EVENTBIT Thomas Haller
2023-09-19 12:18 ` Pablo Neira Ayuso
2023-09-19 12:30   ` Thomas Haller [this message]
2023-09-19 16:20     ` Pablo Neira Ayuso

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=38547bfa61da64801d1cb79f757b40ca1e0c44f4.camel@redhat.com \
    --to=thaller@redhat.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).