All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets
Date: Sat, 7 Dec 2019 12:03:07 +0100	[thread overview]
Message-ID: <20191207110307.GK14469@orbyte.nwl.cc> (raw)
In-Reply-To: <20191206193938.7jceb5dvi2zwkm2g@salvia>

Hi Pablo,

On Fri, Dec 06, 2019 at 08:39:38PM +0100, Pablo Neira Ayuso wrote:
> On Fri, Dec 06, 2019 at 08:26:47PM +0100, Pablo Neira Ayuso wrote:
> > On Thu, Dec 05, 2019 at 11:04:08PM +0100, Phil Sutter wrote:
> > > Hi Pablo,
> > > 
> > > On Thu, Dec 05, 2019 at 07:07:06PM +0100, Pablo Neira Ayuso wrote:
> > > > The existing rbtree implementation might store consecutive elements
> > > > where the closing element and the opening element might overlap, eg.
> > > > 
> > > > 	[ a, a+1) [ a+1, a+2)
> > > > 
> > > > This patch removes the optimization for non-anonymous sets in the exact
> > > > matching case, where it is assumed to stop searching in case that the
> > > > closing element is found. Instead, invalidate candidate interval and
> > > > keep looking further in the tree.
> > > > 
> > > > This patch fixes the lookup and get operations.
> > > 
> > > I didn't get what the actual problem is?
> > 
> > The lookup/get results false, while there is an element in the rbtree.
> > Moreover, the get operation returns true as if a+2 would be in the
> > tree. This happens with named sets after several set updates, I could
> > reproduce the issue with several elements mixed with insertion and
> > deletions in one batch.
> 
> To extend the problem description: The issue is that the existing
> lookup optimization (that only works for the anonymous sets) might not
> reach the opening [ a+1, ... element if the closing ... , a+1) is
> found in first place when walking over the rbtree. Hence, walking the
> full tree in that case is needed.

Ah! Thanks a lot for your elaborations. It was really hard to grasp what
all this is about from the initial commit message. :)

Sometimes I wonder if we should do more set optimizations under the hood
when adding elements. Right now, we don't touch existing ones although
it would make sense. And we could be more intelligent for example if a
set contains 20-30 and a user adds 25-35.

Cheers, Phil

  reply	other threads:[~2019-12-07 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 18:07 [PATCH nf] netfilter: nft_set_rbtree: bogus lookup/get on consecutive elements in named sets Pablo Neira Ayuso
2019-12-05 22:04 ` Phil Sutter
2019-12-06 19:26   ` Pablo Neira Ayuso
2019-12-06 19:39     ` Pablo Neira Ayuso
2019-12-07 11:03       ` Phil Sutter [this message]
2019-12-07 18: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=20191207110307.GK14469@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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.