From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Anders K. Pedersen | Cohaesio" <akp@cohaesio.com>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nftables] Allow concatenation of rt nexthop etc.
Date: Mon, 31 Oct 2016 15:08:33 +0100 [thread overview]
Message-ID: <20161031140833.GA20216@salvia> (raw)
In-Reply-To: <1477734549.1059.65.camel@cohaesio.com>
On Sat, Oct 29, 2016 at 09:49:09AM +0000, Anders K. Pedersen | Cohaesio wrote:
> From: Anders K. Pedersen <akp@cohaesio.com>
>
> Concatenations of rt nexthop or ct {orignal | reply} {saddr | daddr} fail
> due to
>
> # nft add rule ip filter postrouting flow table acct \{ ip saddr . rt nexthop counter \}
> <cmdline>:1:61-70: Error: can not use variable sized data types (invalid) in concat expressions
> add rule ip filter postrouting flow table acct { ip saddr . rt nexthop counter }
> ~~~~~~~~~~~^^^^^^^^^^
>
> Fix this by reordering the check for variable size data types in
> expr_evaluate_concat() to happen after expr_evaluate() has been called (via
> list_member_evaluate()) for the sub expression. This allows
> expr_evaluate_[cr]t() to call [cr]t_expr_update_type() and set the data type
> before the check.
Applied, thanks Anders.
P.S: I can see git am sometimes complain about trailing CRLF, also
patchwork seems to skip some of your patches for some reason, which
makes it easier for us to lose stuff from you. I guess it's probably
MUA related problem, it would be great if you find the root cause.
prev parent reply other threads:[~2016-10-31 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 9:49 [PATCH nftables] Allow concatenation of rt nexthop etc Anders K. Pedersen | Cohaesio
2016-10-31 14:08 ` Pablo Neira Ayuso [this message]
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=20161031140833.GA20216@salvia \
--to=pablo@netfilter.org \
--cc=akp@cohaesio.com \
--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 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.