libiptc memory leak - PATCH

Harald Welte
Fri, 2 May 2003 17:21:47 +0200

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, May 02, 2003 at 04:14:19PM +0200, Martin Josefsson wrote:
> On Fri, 2003-05-02 at 15:47, Martin Josefsson wrote:
> > On Fri, 2003-05-02 at 14:47, Martin Josefsson wrote:
> >=20
> > > This patch breaks {ip,ip6}tables-{save,restore} and it runs free() on
> > > the wrong memoryaddress (I think free() does the right thing anyway b=
> > > the patch still breaks stuff).
> >=20
> > Ok, I was wrong, it did free on a correct memoryaddress, I'll fix up my
> > patch and resend, sorry about that.
> Here's an updated patch that fixes the memory-leak in the previous one.

applied this one instead of the other.

> This should fix it correctly (I hope), iptables, iptables-{save,restore}
> works fine.

we'll see.  I think iptables-1.2.9 is in a quite distant future, so
I hope we discover any potentially introduced bugs until then.

> /Martin

- Harald Welte <>   
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see