From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 0/3] nftables: add support for wildcard interfaces
Date: Mon, 2 May 2022 20:58:56 +0200 [thread overview]
Message-ID: <YnAp8E2JIjD8fm/6@salvia> (raw)
In-Reply-To: <20220429183239.5569-1-fw@strlen.de>
On Fri, Apr 29, 2022 at 08:32:36PM +0200, Florian Westphal wrote:
> First patch is needed so kernel doesn't think end is before start,
> second patch allows to dump "x .foo*" correctly, without this
> nft tries to represent the start/end "name" with a range.
> This doesn't work well because end range uses \ff padding.
>
> Patch 3 adds tests.
LGTM, thanks
prev parent reply other threads:[~2022-05-02 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 18:32 [PATCH nft 0/3] nftables: add support for wildcard interfaces Florian Westphal
2022-04-29 18:32 ` [PATCH nft 1/3] netlink: swap byteorder for host-endian concat data Florian Westphal
2022-04-29 18:32 ` [PATCH nft 2/3] segtree: add pretty-print support for wildcard strings in concatenated sets Florian Westphal
2022-04-29 18:32 ` [PATCH nft 3/3] sets_with_ifnames: add test case for concatenated range Florian Westphal
2022-05-02 18:58 ` 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=YnAp8E2JIjD8fm/6@salvia \
--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