All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira <pablo@eurodev.net>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] Drop expectation refcount after unlinking expectation
Date: Fri, 05 Aug 2005 12:43:04 +0200	[thread overview]
Message-ID: <42F342B8.7010001@trash.net> (raw)
In-Reply-To: <42F2B507.8070207@eurodev.net>

Pablo Neira wrote:
> This fixes the problem although I think that there's something wrong
> with current refcounting. Every time an expectation is created, the
> refcount of the master conntrack is incremented. Then, if the master
> conntrack is destroyed, say the timeout has expired,
> ip_ct_remove_expectation will be called. So firstly, all expectations
> linked to such conntrack are destroyed and then the conntrack itself.
> OK, my question is: why do we need to increase the master conntrack
> refcount for expectations, if they are always killed first? Actually I
> think that the master conntrack refcount should be increased once the
> expectation is confirmed but not in ip_conntrack_expect_alloc.

Only outstanding expectations are removed by remove_expectations().
The fullfilled ones need the reference for stuff like
ip_nat_follow_master.

  parent reply	other threads:[~2005-08-05 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05  0:38 [PATCH] Drop expectation refcount after unlinking expectation Pablo Neira
2005-08-05 10:21 ` Patrick McHardy
2005-08-05 13:17   ` Harald Welte
2005-08-06 14:29     ` Patrick McHardy
2005-08-05 10:43 ` Patrick McHardy [this message]
2005-08-05 13:08   ` Harald Welte
2005-08-06 14:24     ` Patrick McHardy
2005-08-08  0:59       ` Yasuyuki KOZAKAI
2005-08-05 13:20 ` 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=42F342B8.7010001@trash.net \
    --to=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@eurodev.net \
    /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.