From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andrew Beverley <andy@andybev.com>
Cc: netfilter@vger.kernel.org
Subject: Re: libnetfilter_conntrack callbacks and nfct_destroy
Date: Tue, 03 Aug 2010 15:19:48 +0200 [thread overview]
Message-ID: <4C581774.6050800@netfilter.org> (raw)
In-Reply-To: <1280816654.1349.643.camel@andybev>
On 03/08/10 08:24, Andrew Beverley wrote:
> I have 2 questions regarding libnetfilter_conntrack please:
>
> - When using nfct_callback_register() and then nfct_query(), is the
> callback that is subsequently generated a synchronous callback? (It
> appears to be, I'd just like positive confirmation).
The callback is invoked if we succesfully receive the reply message from
the ctnetlink subsystem.
> - Should nfct_destroy() be called after each use of nfct_new() to
> prevent memory leaks? I assume that the answer is yes, but only one of
> the examples in the source code use it.
Yes, nfct_new() requires nfct_destroy() afterwards in order to avoid
memory leaks.
prev parent reply other threads:[~2010-08-03 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 6:24 libnetfilter_conntrack callbacks and nfct_destroy Andrew Beverley
2010-08-03 13:19 ` Pablo Neira Ayuso [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=4C581774.6050800@netfilter.org \
--to=pablo@netfilter.org \
--cc=andy@andybev.com \
--cc=netfilter@vger.kernel.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