Linux Netfilter development
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] nft_set_rbtree: Drop spurious condition for overlap detection on insertion
Date: Wed, 1 Apr 2020 17:02:32 +0200	[thread overview]
Message-ID: <20200401170232.463144f7@elisabeth> (raw)
In-Reply-To: <0ac4c2d001cfed74d3c2304151d7a44105f47552.1585752835.git.sbrivio@redhat.com>

On Wed,  1 Apr 2020 16:54:45 +0200
Stefano Brivio <sbrivio@redhat.com> wrote:

> Case a1. for overlap detection in __nft_rbtree_insert() is not a valid
> one: start-after-start is not needed to detect any type of interval
> overlap and it actually results in a false positive if, while
> descending the tree, this is the only step we hit after starting from
> the root.

Sorry, please disregard, I sent the wrong version. v2 coming in a few
minutes.

-- 
Stefano


      reply	other threads:[~2020-04-01 15:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 14:54 [PATCH nf] nft_set_rbtree: Drop spurious condition for overlap detection on insertion Stefano Brivio
2020-04-01 15:02 ` Stefano Brivio [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=20200401170232.463144f7@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=phil@nwl.cc \
    /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