From: Anton <anton.vazir@gmail.com>
To: Eric Leblond <eric@inl.fr>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: nlif_open() - nlif_close() - memory leak?
Date: Thu, 22 May 2008 12:52:41 +0500 [thread overview]
Message-ID: <200805221252.41392.anton.vazir@gmail.com> (raw)
In-Reply-To: <20080522074319.GD7436@bayen.regit.org>
On Thursday 22 May 2008 12:43, Eric Leblond wrote:
> Hello,
>
> On Thursday, 2008 May 22 at 10:53:40 +0500, Anton wrote:
> You should not call nlif_open, nlif_close at each
> resolution:
Yes, this is obvious, it was just a quick test.
>
> Information about nlif usage:
> http://software.inl.fr/trac/wiki/articles/using_nlif
Great, thanks!
>
> Anyway, I will investigate to see what's going on. We
> definitely should not have a memory leak.
>
> BR,
next prev parent reply other threads:[~2008-05-22 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 5:53 nlif_open() - nlif_close() - memory leak? Anton
2008-05-22 7:43 ` Eric Leblond
2008-05-22 7:52 ` Anton [this message]
2008-05-22 8:07 ` Eric Leblond
-- strict thread matches above, loose matches on Subject: below --
2008-05-22 10:00 Anton
2008-05-22 12:48 ` Eric Leblond
2008-05-22 13:08 ` Pablo Neira Ayuso
2008-05-22 14:11 ` Eric Leblond
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=200805221252.41392.anton.vazir@gmail.com \
--to=anton.vazir@gmail.com \
--cc=eric@inl.fr \
--cc=netfilter-devel@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 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.