All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next 0/5] netfilter: conntrack: rework nf_ct_iterate, part 1.
Date: Mon, 29 May 2017 11:35:32 +0200	[thread overview]
Message-ID: <20170529093532.GA10029@salvia> (raw)
In-Reply-To: <20170521105259.10239-1-fw@strlen.de>

On Sun, May 21, 2017 at 12:52:54PM +0200, Florian Westphal wrote:
> First batch of changes to rework how we iterate over the conntrack table.
> 
> Historically, we had one table.
> When net namespaces were added, we got one table per namespace.
> Nowadays we again only have a single table (which considers netns
> during lookups).
> 
> This series prepares for removal of some open-coded table iteration
> places.
> 
> It also adds nf_ct_iterate_destroy(), to be used in module exit path
> when we need to inspect every conntrack entry regardless of namespace,
> then uses it from nat module exit path.

Series applied, thanks.

      parent reply	other threads:[~2017-05-29  9:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21 10:52 [PATCH nf-next 0/5] netfilter: conntrack: rework nf_ct_iterate, part 1 Florian Westphal
2017-05-21 10:52 ` [PATCH nf-next 1/5] netfilter: conntrack: rename nf_ct_iterate_cleanup Florian Westphal
2017-05-21 10:52 ` [PATCH nf-next 2/5] netfilter: conntrack: don't call iter for non-confirmed conntracks Florian Westphal
2017-05-21 10:52 ` [PATCH nf-next 3/5] netfilter: conntrack: add nf_ct_iterate_destroy Florian Westphal
2017-05-21 10:52 ` [PATCH nf-next 4/5] netfilter: conntrack: restart iteration on resize Florian Westphal
2017-05-21 10:52 ` [PATCH nf-next 5/5] netfilter: nat: destroy nat mappings on module exit path only Florian Westphal
2017-05-29  9:35 ` Pablo Neira Ayuso [this message]

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=20170529093532.GA10029@salvia \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.