From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [PATCH net] ipv6: Fix cleanup ordering on inet6_init() error path
Date: Thu, 11 Jan 2018 16:48:56 +0000 [thread overview]
Message-ID: <1515689336.12097.14.camel@codethink.co.uk> (raw)
In-Reply-To: <CAM_iQpXLgGLq8BgTeL5R3hB=8nb_jYgmb+uGE9BsGBgt=SMEjg@mail.gmail.com>
On Wed, 2018-01-10 at 14:25 -0800, Cong Wang wrote:
> On Tue, Jan 9, 2018 at 10:21 AM, Ben Hutchings
> <ben.hutchings@codethink.co.uk> wrote:
> > Commit 15e668070a64 reordered the initialisation in inet6_init() to
> > fix a crash on an error path further down the call stack. It also
> > reordered cleanup on the error path in inet6_init(), but the result
> > is not the reverse of the initialisation order. This presumably
> > can result in a resource leak or crash in some error
> > cases. Reorder
> > cleanup again to fix this.
>
> Can you be specific on what resource we leak here?
If icmpv6_init() fails, after ip6_mr_init(), then ip6_mr_cleanup() is
not called.
Also, if ip6_mr_init() fails, we don't unregister inet6_net_ops. I
think that will result in a crash - immediately if ipv6 is a module,
otherwise when the next net namespace is created.
> Also, it looks like you not just revert the order changed in commit
> 15e668070a64, but also you move icmpv6_cleanup() even earlier.
So should I add another Fixes: there?
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-01-11 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 18:21 [PATCH net] ipv6: Fix cleanup ordering on inet6_init() error path Ben Hutchings
2018-01-10 22:25 ` Cong Wang
2018-01-11 16:48 ` Ben Hutchings [this message]
2018-01-13 17:38 ` Cong Wang
2018-01-13 17:39 ` Cong Wang
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=1515689336.12097.14.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=andreyknvl@google.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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).