From: Sam Roberts <vieuxtech@gmail.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] rework of userspace expectation support
Date: Tue, 17 May 2011 14:12:19 -0700 [thread overview]
Message-ID: <BANLkTinreLDGTuQ0tH+KyHVuB7XHckzYzA@mail.gmail.com> (raw)
In-Reply-To: <4DB02DAC.1070406@netfilter.org>
Patrick, are you going to merge these?
I don't see it in nf-next-2.6.git.
On Thu, Apr 21, 2011 at 6:14 AM, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On 20/04/11 16:06, Patrick McHardy wrote:
>> I thought this is what your patches try to fix?
>
> Yes, my patches add the helper extension to the conntrack by means of
> the CT target. Thus, in the case of userspace helpers, the master
> conntrack can store the list of unfulfilled expectations that it owns.
Its not clear to me why the CT master isn't added on a master-less
connection at the time that a userspace expectation is set (instead of
having to use the CT target in the raw table to create the master for
all connections that might potentially need a userspace expectation).
However, I'll take any fix that stops the oopsing.
Thanks,
Sam
next prev parent reply other threads:[~2011-05-17 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 21:59 [PATCH 0/2] rework of userspace expectation support Pablo Neira Ayuso
2011-04-12 21:59 ` [PATCH 1/2] netfilter: CT: allow to set userspace helper status flag Pablo Neira Ayuso
2011-04-12 21:59 ` [PATCH 2/2] netfilter: nf_ct_expect: rework userspace expectation support Pablo Neira Ayuso
2011-04-13 11:37 ` [PATCH 0/2] rework of " Patrick McHardy
2011-04-13 11:47 ` Pablo Neira Ayuso
2011-04-13 11:55 ` Patrick McHardy
2011-04-13 12:11 ` Pablo Neira Ayuso
2011-04-13 12:28 ` Patrick McHardy
2011-04-13 20:02 ` Pablo Neira Ayuso
2011-04-20 12:10 ` Pablo Neira Ayuso
2011-04-20 14:06 ` Patrick McHardy
2011-04-21 13:14 ` Pablo Neira Ayuso
2011-05-17 21:12 ` Sam Roberts [this message]
2011-06-13 21:57 ` Sam Roberts
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=BANLkTinreLDGTuQ0tH+KyHVuB7XHckzYzA@mail.gmail.com \
--to=vieuxtech@gmail.com \
--cc=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).