All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailing list
	<netfilter-devel@vger.kernel.org>,
	Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [PATCH nf,v2] netfilter: nf_tables: release objects on netns destruction
Date: Fri, 11 Dec 2015 09:33:20 +0100	[thread overview]
Message-ID: <CAOkSjBin2WoyFtp6aDOh1fHFHS4cfCKotaqy7m0Y8epY_GMgUA@mail.gmail.com> (raw)
In-Reply-To: <1449690931-1617-1-git-send-email-pablo@netfilter.org>

On 9 December 2015 at 20:55, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> We have to release the existing objects on netns removal otherwise we
> leak them. Chains are unregistered in first place to make sure no
> packets are walking on our rules and sets anymore.
>
> Reported-by: Patrick McHardy <kaber@trash.net>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> v2: Unregister chains in first place to make sure no packets are walking
>     over rules and sets anymore.
>
>  net/netfilter/nf_tables_api.c | 43 ++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 42 insertions(+), 1 deletion(-)
>

I've run a kernel with this patch, did some tests regarding netns and
nftables, and found no problems so far :-)

Tested-by: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>

-- 
Arturo Borrero González
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-12-11  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 19:55 [PATCH nf,v2] netfilter: nf_tables: release objects on netns destruction Pablo Neira Ayuso
2015-12-11  8:33 ` Arturo Borrero Gonzalez [this message]
2015-12-13 21:42 ` Pablo Neira Ayuso

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=CAOkSjBin2WoyFtp6aDOh1fHFHS4cfCKotaqy7m0Y8epY_GMgUA@mail.gmail.com \
    --to=arturo.borrero.glez@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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.