From: Patrick McHardy <kaber@trash.net>
To: adobriyan@gmail.com
Cc: 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: Thu, 04 Sep 2008 18:54:16 +0200 [thread overview]
Message-ID: <48C012B8.10606@trash.net> (raw)
In-Reply-To: <20080821220432.GT31136@x200.localdomain>
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.
>
> struct netns_ct {
> atomic_t count;
> @@ -12,5 +13,7 @@ struct netns_ct {
> struct hlist_head *expect_hash;
> int expect_vmalloc;
> struct hlist_head unconfirmed;
> + /* Fake conntrack entry for untracked connections */
> + struct nf_conn untracked;
> };
next prev parent reply other threads:[~2008-09-04 16: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 [this message]
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
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=48C012B8.10606@trash.net \
--to=kaber@trash.net \
--cc=adobriyan@gmail.com \
--cc=containers@lists.linux-foundation.org \
--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).