Netdev List
 help / color / mirror / Atom feed
From: adobriyan@gmail.com
To: Jan Engelhardt <jengelh@medozas.de>
Cc: kaber@trash.net, 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, 22 Aug 2008 15:30:28 +0400	[thread overview]
Message-ID: <20080822113028.GB2321@x200.localdomain> (raw)
In-Reply-To: <alpine.LNX.1.10.0808211903000.20596@fbirervta.pbzchgretzou.qr>

On Thu, Aug 21, 2008 at 07:06:37PM -0400, Jan Engelhardt wrote:
> On Thursday 2008-08-21 18:04, adobriyan@gmail.com wrote:
> 
> >Make untracked conntrack per-netns.
> 
> Why? It does not store any useful information per se, it is
> merely used to add a third type of ct, iow:
> 
> (a) ct==NULL
> (b) ct!=NULL
> (c) ct==&untracked
> 
> mmap(2)'s return value for example has something similar:
> 
> (a) mmap(...)==NULL
> (b) mmap(...)==MMAP_FAILED
> (c) otherwise
> 
> The untracked ct is a singleton, and should stay one, unless
> there are further reasons not to do so.

We wait for untracked ct refcount to drop to 1 back:

	/* wait until all references to nf_conntrack_untracked are dropped */
	while (atomic_read(&nf_conntrack_untracked.ct_general.use) > 1)
		schedule();

Consequently it should be one per netns, otherwise netns A can prevent
netns B from stopping.


  reply	other threads:[~2008-08-22 11:30 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 [this message]
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
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=20080822113028.GB2321@x200.localdomain \
    --to=adobriyan@gmail.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=jengelh@medozas.de \
    --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