From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Refcounts in libnftnl?
Date: Sat, 18 May 2019 09:36:28 +0200 [thread overview]
Message-ID: <20190518073628.GH4851@orbyte.nwl.cc> (raw)
Hi!
Probably the best way to fix for the segfaults caused by Florian's cache
rebuild logic in iptables-nft is to introduce reference counts so we
don't have to care about whether a given object is present only in cache
or also in a batch job.
Unlike nftables, iptables-nft code uses libnftnl data structures instead
of its own ones.
I wonder if it is OK to add refcounts to libnftnl types instead of
implementing wrapper structures for everything in iptables-nft. What do
you think?
Cheers, Phil
reply other threads:[~2019-05-18 7:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190518073628.GH4851@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=fw@strlen.de \
--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 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).