From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: ctnetlink: add expectation deletion events
Date: Tue, 19 Oct 2010 10:20:10 +0200 [thread overview]
Message-ID: <4CBD54BA.3040306@trash.net> (raw)
In-Reply-To: <4CB8847E.4030004@netfilter.org>
Am 15.10.2010 18:42, schrieb Pablo Neira Ayuso:
> On 15/10/10 17:44, Patrick McHardy wrote:
>> Am 14.10.2010 14:02, schrieb Pablo Neira Ayuso:
>>> This patch allows to listen to events that inform about
>>> expectations destroyed.
>>
>> This looks fine, but I'm wondering why we're not delivering
>> events for expectations created and destroyed by helpers using
>> nf_conntrack_expect_related()/nf_conntrack_unexpect_related().
>
> We already deliver events for new expectations. Wrt. destroyed
> expectations, nf_ct_unexpect_related() internally calls
> nf_ct_unlink_expect(), so they are also delivered.
I see. Applied, thanks Pablo.
prev parent reply other threads:[~2010-10-19 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 12:02 [PATCH] netfilter: ctnetlink: add expectation deletion events Pablo Neira Ayuso
2010-10-15 15:44 ` Patrick McHardy
2010-10-15 16:42 ` Pablo Neira Ayuso
2010-10-19 8:20 ` 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=4CBD54BA.3040306@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).