All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org, admin@rollinix.net,
	niels@kristensen.io, tom@compton.nu
Subject: Re: [PATCH nft 3/3] rule: fix use of intervals in set declarations
Date: Fri, 19 Jun 2015 15:59:58 +0200	[thread overview]
Message-ID: <20150619135958.GA19487@salvia> (raw)
In-Reply-To: <20150619134444.GL22946@acer.localdomain>

On Fri, Jun 19, 2015 at 03:44:44PM +0200, Patrick McHardy wrote:
> On 19.06, Pablo Neira Ayuso wrote:
> > On Fri, Jun 19, 2015 at 03:13:36PM +0200, Patrick McHardy wrote:
> > > >  static int do_add_setelems(struct netlink_ctx *ctx, const struct handle *h,
> > > > -			   const struct expr *expr)
> > > > +			   const struct location *loc, struct expr *expr)
> > > >  {
> > > > -	if (netlink_add_setelems(ctx, h, expr) < 0)
> > > > +	struct set *set;
> > > > +
> > > > +	if (netlink_get_set(ctx, h, loc) < 0)
> > > 
> > > I think we should get it from the internal list and not from the
> > > kernel.
> > 
> > There is no such internal list at this moment, we retrieve the list
> > only for do_command_list(). Are you suggesting to add the code to
> > retrieve it inconditionally initially?
> 
> We do have the table->sets list. Yeah, but we don't add it to that
> list in the creation part, I see. Actually we should be doing that,
> since otherwise we also won't support creating a set and adding
> new elements in seperate commands but a single transaction.

Right.

> > > We can't add intervals to existing sets so far anyways, and this
> > > would allow it, but it wouldn't work.
> > 
> > Not sure what you mean with this.
> 
> Intervals need to know the entire set content to be created correctly.
> We don't handle incremental updates with intervals correctly ATM.

What's the problem?
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in

  reply	other threads:[~2015-06-19 13:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 13:15 [PATCH nft 1/3] rule: use netlink_add_setelems() when creating literal sets Pablo Neira Ayuso
2015-06-19 13:15 ` [PATCH nft 2/3] segtree: pass element expression as parameter to set_to_intervals() Pablo Neira Ayuso
2015-06-19 13:15 ` [PATCH nft 3/3] rule: fix use of intervals in set declarations Pablo Neira Ayuso
2015-06-19 13:13   ` Patrick McHardy
2015-06-19 13:48     ` Pablo Neira Ayuso
2015-06-19 13:44       ` Patrick McHardy
2015-06-19 13:59         ` Pablo Neira Ayuso [this message]
2015-06-19 13:59           ` Patrick McHardy
2015-06-19 17:40             ` Pablo Neira Ayuso
2015-06-19 18:01               ` Patrick McHardy
2015-06-19 18:15               ` Patrick McHardy
2015-06-20 11:06                 ` Pablo Neira Ayuso
2015-06-20 11:41                   ` Patrick McHardy
2015-06-20 18:37                     ` 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=20150619135958.GA19487@salvia \
    --to=pablo@netfilter.org \
    --cc=admin@rollinix.net \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=niels@kristensen.io \
    --cc=tom@compton.nu \
    /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.