From: "Tomáš Lejdar" <tomas.lejdar@i.cz>
To: Harald Welte <laforge@netfilter.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: libiptc memory leak - PATCH
Date: Mon, 28 Apr 2003 09:14:25 +0200 [thread overview]
Message-ID: <3EACD4D1.90704@i.cz> (raw)
In-Reply-To: <20030427125345.GD990@sunbeam.de.gnumonks.org>
Hi,
I thing there is no problem, the memory is freed only when the
function next_chain returns NULL and run through the chains is on the end.
In the next call of first_chain() is memory alocated again in
populate_cache().
Is there something wrong in my idea ?
T.v.L
Harald Welte wrote:
I cannot accept this patch It would basically mean that something like:
>first_chain()
>next_chain()
>first_chain()
>
>would no longer work.
>
>we need an explicit free_handle that cleans up all allocated regions
>instead. Patches are welcome.
>
>
next prev parent reply other threads:[~2003-04-28 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 22:25 libiptc memory leak - PATCH Tomáš Lejdar
2003-04-27 12:51 ` Harald Welte
2003-04-27 12:53 ` Harald Welte
2003-04-28 7:14 ` Tomáš Lejdar [this message]
2003-04-30 15:47 ` Harald Welte
2003-05-02 12:47 ` Martin Josefsson
2003-05-02 13:47 ` Martin Josefsson
2003-05-02 14:14 ` Martin Josefsson
2003-05-02 15:21 ` Harald Welte
2003-05-03 20:52 ` Martin Josefsson
2003-05-02 15:14 ` Harald Welte
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=3EACD4D1.90704@i.cz \
--to=tomas.lejdar@i.cz \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.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.