Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] src: allow to map key to nfqueue number
Date: Wed, 6 Nov 2024 17:03:55 +0100	[thread overview]
Message-ID: <ZyuTa9lmkXRAvSfn@calendula> (raw)
In-Reply-To: <20241106143253.GA12653@breakpoint.cc>

Hi Florian,

On Wed, Nov 06, 2024 at 03:32:53PM +0100, Florian Westphal wrote:
> Florian Westphal <fw@strlen.de> wrote:
> > > From userdata path it should be possible to check for this special
> > > internal queue_datatype then encode the queue number type in the TLV.
> > 
> > I have no idea how to do any of this.  I don't even know what a "queue number
> > type" is.
> > 
> > How on earth do i flip the data type on postprocessing without any idea
> > what "2 octets worth of data" is?
> 
> You seem to dislike EXPR_TYPE; I tried to sketch something but i would
> turn EXPR_VALUE into EXPR_TYPE, including EXPR_TYPEOF_NFQUEUE_ID and
> the udata build/parse functions, with the addition of a
> 
>  /* Dummy alias of integer_type for nf_queue id numbers */
>  const struct datatype integer_queue_type = {
> 
> that has no actual function except to override what constant_expr_print()
> ends up doing.

I am fine with your patch, it is perfectly fine to address this in
this way. I just proposed a different way to handle this special case.

I can take a look later today based on your patch, I think I can reuse
90% of it, it is just a subtle detail what I am referring to.

  reply	other threads:[~2024-11-06 16:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25  7:47 [PATCH nft] src: allow to map key to nfqueue number Florian Westphal
2024-11-06 13:28 ` Pablo Neira Ayuso
2024-11-06 13:52   ` Florian Westphal
2024-11-06 14:32     ` Florian Westphal
2024-11-06 16:03       ` Pablo Neira Ayuso [this message]
2024-11-06 23:11         ` Pablo Neira Ayuso
2024-11-06 23:34           ` Pablo Neira Ayuso
2024-11-08 12:08             ` Florian Westphal
2024-11-11 10:38               ` 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=ZyuTa9lmkXRAvSfn@calendula \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox