All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: nft cache updates
Date: Mon, 9 Nov 2015 15:30:56 +0000	[thread overview]
Message-ID: <20151109153055.GI8098@macbook.localdomain> (raw)

Hi Pablo,

I'm wondering what the rational for the current cache update behaviour is.
The changelog states it is somehow related to the requested command, but
that doesn't seem to be true.

Even "nft describe" fails with EPERM as user since the cache appears to be
initialized unconditionally, which is a bit unfortunate. Also I used to
test things parsing, evaluation and even netlink generation without actually
adding those rules as user, which does not work anymore. This might be harder
to get working again, but I'm not sure why we do a full initialization anyways.
The only thing that appears to be needed are sets, and those only in some
specific circumstances.

Cheers,
Patrick

             reply	other threads:[~2015-11-09 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 15:30 Patrick McHardy [this message]
2015-11-09 16:48 ` nft cache updates Pablo Neira Ayuso
2015-11-09 17:05   ` Patrick McHardy
2015-11-09 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=20151109153055.GI8098@macbook.localdomain \
    --to=kaber@trash.net \
    --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.