From: Pavel Emelyanov <xemul@openvz.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
devel@openvz.org, den@openvz.org
Subject: Re: unlock iptables in netns
Date: Mon, 16 Jun 2008 15:17:36 +0400 [thread overview]
Message-ID: <48564BD0.3010006@openvz.org> (raw)
In-Reply-To: <48564B70.2020400@trash.net>
Patrick McHardy wrote:
> Alexey Dobriyan wrote:
>> On Mon, Jun 16, 2008 at 12:26:03PM +0200, Patrick McHardy wrote:
>>> By the way, is there already work done for conntrack/NAT namespace
>>> support? I have this patch that uses marks for something very similar
>>> that should be easy to adjust.
>> Yes, right now I'm fighting something which looks like double free
>> of conntrack during clone(CLONE_NEWNET)/exit test despite none created
>> in netns. And unknown to me dimensions of input and output packet codepaths.
>> :^)
>>
>> Preliminaty details:
>> struct nf_conn::ct_net which pins netns
>
> From the VLAN code, I thought namespaces could also be identified
> numerically. That would reduce the size increase of struct nf_conn.
Numerically? I made VLAN-s netnsization, but everything was spinning
around the struct net *pointer*. Can you elaborate on this?
>> netns of expectation is netns of master conntrack by definition
>> per-netns conntrack hash
>> per-netns expect hash
>> per-netns unconfirmed list
>
> That all makes sense.
>
>
next prev parent reply other threads:[~2008-06-16 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:27 unlock iptables in netns Alexey Dobriyan
2008-06-11 6:53 ` Patrick McHardy
2008-06-16 10:26 ` Patrick McHardy
2008-06-16 11:04 ` Alexey Dobriyan
2008-06-16 11:16 ` Patrick McHardy
2008-06-16 11:17 ` Pavel Emelyanov [this message]
2008-06-16 11:21 ` Patrick McHardy
2008-06-20 17:54 ` Alexey Dobriyan
2008-06-21 8:03 ` 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=48564BD0.3010006@openvz.org \
--to=xemul@openvz.org \
--cc=adobriyan@gmail.com \
--cc=den@openvz.org \
--cc=devel@openvz.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).