From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: netfilter-devel@vger.kernel.org, Andreas Fischer <netfilter@d9c.eu>
Subject: Re: [PATCH nf 0/2] nft_set_rbtree: Two fixes for overlap detection on insert
Date: Fri, 21 Aug 2020 19:46:56 +0200 [thread overview]
Message-ID: <20200821174656.GA1980@salvia> (raw)
In-Reply-To: <cover.1597873312.git.sbrivio@redhat.com>
On Wed, Aug 19, 2020 at 11:59:13PM +0200, Stefano Brivio wrote:
> Patch 1/2 fixes false positive cases resulting from a flawed
> assumption highlighted by
> https://bugzilla.netfilter.org/show_bug.cgi?id=1449
> and is addressed for stable (5.6.x).
>
> Patch 2/2 fixes a false negative case I noticed while skipping
> different interval overlap checks in nft.
Applied, thanks.
prev parent reply other threads:[~2020-08-21 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 21:59 [PATCH nf 0/2] nft_set_rbtree: Two fixes for overlap detection on insert Stefano Brivio
2020-08-19 21:59 ` [PATCH nf 1/2] nft_set_rbtree: Handle outcomes of tree rotations in overlap detection Stefano Brivio
2020-08-19 21:59 ` [PATCH nf 2/2] nft_set_rbtree: Detect partial overlap with start endpoint match Stefano Brivio
2020-08-21 17:46 ` 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=20200821174656.GA1980@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@d9c.eu \
--cc=sbrivio@redhat.com \
/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).