From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] ctnetlink: optional packet drop to make event delivery reliable
Date: Tue, 24 Mar 2009 15:04:26 +0100 [thread overview]
Message-ID: <49C8E86A.6060707@netfilter.org> (raw)
In-Reply-To: <49C8E514.2010205@trash.net>
Patrick McHardy wrote:
> But it seems rather pointless to add it in this state, it doesn't
> increase reliability one bit. Additionally reversing the order of
> state transitions and event delivery seems like a highly intrusive
> change since event delivery obviously already needs to know the
> new state, meaning we'd need to record all state changes, then
> deliver the event, then "commit" them. So I'd like to see what
> we're engaging in before merging this half finished patch.
I see, I'm going to send you a new patch so we can discuss on something
in particular.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2009-03-24 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 11:07 [PATCH] ctnetlink: optional packet drop to make event delivery reliable Pablo Neira Ayuso
2009-03-24 13:21 ` Patrick McHardy
2009-03-24 13:41 ` Pablo Neira Ayuso
2009-03-24 13:50 ` Patrick McHardy
2009-03-24 14:04 ` Pablo Neira Ayuso [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=49C8E86A.6060707@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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.