From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: nf_nat: fix oops on netns removal
Date: Mon, 16 Jun 2014 14:00:25 +0200 [thread overview]
Message-ID: <20140616120025.GA10876@localhost> (raw)
In-Reply-To: <1402168624-10081-1-git-send-email-fw@strlen.de>
On Sat, Jun 07, 2014 at 09:17:04PM +0200, Florian Westphal wrote:
> Quoting Samu Kallio:
>
> Basically what's happening is, during netns cleanup,
> nf_nat_net_exit gets called before ipv4_net_exit. As I understand
> it, nf_nat_net_exit is supposed to kill any conntrack entries which
> have NAT context (through nf_ct_iterate_cleanup), but for some
> reason this doesn't happen (perhaps something else is still holding
> refs to those entries?).
>
> When ipv4_net_exit is called, conntrack entries (including those
> with NAT context) are cleaned up, but the
> nat_bysource hashtable is long gone - freed in nf_nat_net_exit. The
> bug happens when attempting to free a conntrack entry whose NAT hash
> 'prev' field points to a slot in the freed hash table (head for that
> bin).
>
> We ignore conntracks with null nat bindings. But this is wrong,
> as these are in bysource hash table as well.
>
> Restore nat-cleaning for the netns-is-being-removed case.
>
> bug:
> https://bugzilla.kernel.org/show_bug.cgi?id=65191
> Fixes: c2d421e1718 ('netfilter: nf_nat: fix race when unloading protocol modules')
Applied, thanks!
prev parent reply other threads:[~2014-06-16 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 19:17 [PATCH] netfilter: nf_nat: fix oops on netns removal Florian Westphal
2014-06-16 12:00 ` 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=20140616120025.GA10876@localhost \
--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 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).