From: Florian Westphal <fw@strlen.de>
To: David Laight <David.Laight@ACULAB.COM>
Cc: 'Florian Westphal' <fw@strlen.de>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH nf-next] netns: add and use net_ns_barrier
Date: Fri, 2 Jun 2017 11:53:42 +0200 [thread overview]
Message-ID: <20170602095342.GC13569@breakpoint.cc> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DD000799C@AcuExch.aculab.com>
David Laight <David.Laight@ACULAB.COM> wrote:
> From: Florian Westphal
> > Sent: 30 May 2017 10:38
> >
> > Quoting Joe Stringer:
> > If a user loads nf_conntrack_ftp, sends FTP traffic through a network
> > namespace, destroys that namespace then unloads the FTP helper module,
> > then the kernel will crash.
> >
> > Events that lead to the crash:
> > 1. conntrack is created with ftp helper in netns x
> > 2. This netns is destroyed
> > 3. netns destruction is scheduled
> > 4. netns destruction wq starts, removes netns from global list
> > 5. ftp helper is unloaded, which resets all helpers of the conntracks
> > via for_each_net()
> >
> > but because netns is already gone from list the for_each_net() loop
> > doesn't include it, therefore all of these conntracks are unaffected.
> >
> > 6. helper module unload finishes
> > 7. netns wq invokes destructor for rmmod'ed helper
> >
> ...
> > void
> > nf_ct_iterate_destroy(int (*iter)(struct nf_conn *i, void *data), void *data)
> > @@ -1734,6 +1736,13 @@ nf_ct_iterate_destroy(int (*iter)(struct nf_conn *i, void *data), void *data)
> > }
> > rtnl_unlock();
> >
> > + /* Need to wait for netns cleanup worker to finish, if its
> > + * running -- it might have deleted a net namespace from
> > + * the global list, so our __nf_ct_unconfirmed_destroy() might
> > + * not have affected all namespaces.
> > + */
> > + net_ns_barrier();
> > +
>
> A problem I see is that nothing obvious guarantees that the cleanup worker
> has actually started.
If it hasn't even started, the earlier for_each_net() has seen all
net namespaces and we managed to clear helper extensions of all conntracks.
Same in case it has finished already: netns cleanup work queue has
free'd all the affected conntracks we might have missed.
We only are in trouble if netns work queue is running concurrently:
netns cleanup first removes net namespaces from the global list,
so nf_ct_iterate_destroy might have missed these.
next prev parent reply other threads:[~2017-06-02 9:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 9:38 [PATCH nf-next] netns: add and use net_ns_barrier Florian Westphal
2017-05-31 16:55 ` David Miller
2017-05-31 17:46 ` Eric W. Biederman
2017-05-31 18:13 ` Eric W. Biederman
2017-05-31 20:21 ` Joe Stringer
2017-06-01 8:52 ` Florian Westphal
2017-06-12 21:47 ` Cong Wang
2017-06-13 6:16 ` Florian Westphal
2017-06-13 16:35 ` Cong Wang
2017-06-13 18:07 ` Florian Westphal
2017-06-13 19:27 ` Joe Stringer
2017-06-13 21:16 ` Cong Wang
2017-06-14 8:41 ` Pablo Neira Ayuso
2017-06-14 14:20 ` Eric W. Biederman
2017-06-12 8:47 ` Pablo Neira Ayuso
2017-06-02 9:38 ` David Laight
2017-06-02 9:53 ` Florian Westphal [this message]
2017-06-19 17:10 ` 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=20170602095342.GC13569@breakpoint.cc \
--to=fw@strlen.de \
--cc=David.Laight@ACULAB.COM \
--cc=ebiederm@xmission.com \
--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).