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>,
Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Subject: Re: [PATCH] Don't increase master refcount on expectations
Date: Sun, 04 Sep 2005 19:47:43 +0200 [thread overview]
Message-ID: <431B333F.8030902@trash.net> (raw)
In-Reply-To: <430E2DF9.8060802@eurodev.net>
Pablo Neira wrote:
> As it's been discussed [1][2]. We shouldn't increase the master
> conntrack refcount for non-fulfilled conntracks. During the conntrack
> destruction, the expectations are always killed before the conntrack
> itself, this guarantees that there won't be any orphan expectation.
Applied, thanks. Is it correct that this also fixes the untriggerable
deadlock Yasuyuki noticed?
next prev parent reply other threads:[~2005-09-04 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 20:45 [PATCH] Don't increase master refcount on expectations Pablo Neira
2005-08-26 12:33 ` JessePeng
2005-09-07 5:01 ` Yasuyuki KOZAKAI
2005-09-11 22:38 ` Jesse Peng
2005-09-04 17:47 ` Patrick McHardy [this message]
2005-09-07 2:00 ` Yasuyuki KOZAKAI
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=431B333F.8030902@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@eurodev.net \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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.