From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
containers@lists.linux-foundation.org
Subject: Re: [PATCH 20/38] netns ct: NOTRACK in netns
Date: Fri, 05 Sep 2008 13:54:29 +0200 [thread overview]
Message-ID: <48C11DF5.9040207@netfilter.org> (raw)
In-Reply-To: <48C11918.8020508@trash.net>
Patrick McHardy wrote:
> Alexey Dobriyan wrote:
>> On Thu, Sep 04, 2008 at 06:54:16PM +0200, Patrick McHardy wrote:
>>> adobriyan@gmail.com wrote:
>>>> Make untracked conntrack per-netns. Compare conntracks with relevant
>>>> untracked one.
>>>>
>>>> The following code you'll start laughing at this code:
>>>>
>>>> if (ct == ct->ct_net->ct.untracked)
>>>> ...
>>>>
>>>> let me remind you that ->ct_net is set in only one place, and never
>>>> overwritten later.
>>>>
>>>> All of this requires some surgery with headers, otherwise horrible
>>>> circular
>>>> dependencies. And we lost nf_ct_is_untracked() as function, it
>>>> became macro.
>>> I think you could avoid this mess by using a struct nf_conntrack
>>> for the untracked conntrack instead of struct nf_conn. It shouldn't
>>> make any difference since its ignored anyways.
>>
>> Ewww, can I?
>
> I hope so :) A different possiblity suggest by Pablo some time ago
> would be to mark untracked packets in skb->nfctinfo and not
> attach a conntrack at all.
Indeed, I remember that :). I left that patch of the table time ago [1].
There's a nf_reset call missing as Patrick said at that time. I can
recover it if you like the idea.
[1]
http://lists.netfilter.org/pipermail/netfilter-devel/2005-June/020171.html
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2008-09-05 11:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 22:04 [PATCH 20/38] netns ct: NOTRACK in netns adobriyan
2008-08-21 23:06 ` Jan Engelhardt
2008-08-22 11:30 ` adobriyan
2008-08-24 0:35 ` Jan Engelhardt
2008-08-24 10:43 ` Alexey Dobriyan
2008-09-04 16:54 ` Patrick McHardy
2008-09-05 2:58 ` Alexey Dobriyan
2008-09-05 4:18 ` Jan Engelhardt
2008-09-05 11:33 ` Patrick McHardy
2008-09-05 11:54 ` Pablo Neira Ayuso [this message]
2008-09-05 12:25 ` Patrick McHardy
2008-09-05 13:08 ` Jan Engelhardt
2008-09-05 13:10 ` Patrick McHardy
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=48C11DF5.9040207@netfilter.org \
--to=pablo@netfilter.org \
--cc=adobriyan@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--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 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).