From: Patrick McHardy <kaber@trash.net>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: hawk@comx.dk, netfilter-devel@lists.netfilter.org,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH] BUG: libiptc chain references bug
Date: Thu, 20 Jul 2006 18:52:06 +0200 [thread overview]
Message-ID: <44BFB4B6.3050307@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0607162125500.31595@ask.diku.dk>
Jesper Dangaard Brouer wrote:
>
> On Sun, 16 Jul 2006, Pablo Neira Ayuso wrote:
>
>> I don't like too much the is-the-rule-in-list checking in
>> delete_entry, please, could you tell me what you think about the patch
>> attached? I think it's cleaner. Thanks.
>
>
> First of all, (no offence) your patch will not work, as it does not
> catch all control-flow cases. That is, if no match was found your patch
> does not decrement the refcount. Hint, look at the places free(r) is
> called.
>
> I have attached a patch, that does catch all cases. This is achived by
> adding a else statement to the if statement where iptcc_map_target is
> called.
>
> I did consider, your strategy, but the reason I decided not to, was that
> I though it was cleaner to always call "iptcc_delete_rule" when we want
> to delete a rule, instead of free'ing it manually.
>
> Well, I think Patrick should make the decision. As long as we fix the
> bug, I don't care which patch goes in.
I like the second patch better than the first one, so I've applied
this one. Thanks Jesper.
prev parent reply other threads:[~2006-07-20 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 15:25 BUG: libiptc chain references bug Jesper Dangaard Brouer
2006-07-13 11:17 ` Jesper Dangaard Brouer
2006-07-14 12:29 ` [PATCH] " Jesper Dangaard Brouer
2006-07-16 15:01 ` Pablo Neira Ayuso
2006-07-16 20:19 ` Jesper Dangaard Brouer
2006-07-16 22:31 ` Pablo Neira Ayuso
2006-07-20 16:52 ` Patrick McHardy [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=44BFB4B6.3050307@trash.net \
--to=kaber@trash.net \
--cc=hawk@comx.dk \
--cc=hawk@diku.dk \
--cc=netfilter-devel@lists.netfilter.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 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.