From: Ying Xue <ying.xue@windriver.com>
To: Cong Wang <cwang@twopensource.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: netns refcount leak
Date: Mon, 9 Mar 2015 17:50:28 +0800 [thread overview]
Message-ID: <54FD6CE4.5040708@windriver.com> (raw)
In-Reply-To: <CAHA+R7PyGGjx_L_fMnBbTf8tgttqrH1d4LvLKR=CFB82CERoEw@mail.gmail.com>
On 03/07/2015 07:29 AM, Cong Wang wrote:
> Hi, Ying
>
>
> The following commit from you causes a netns refcount leak:
>
> a62fbccecd62bacb4416fc427239f5b43b25d05e is the first bad commit
> commit a62fbccecd62bacb4416fc427239f5b43b25d05e
> Author: Ying Xue <ying.xue@windriver.com>
> Date: Fri Jan 9 15:27:11 2015 +0800
>
> tipc: make subscriber server support net namespace
>
> TIPC establishes one subscriber server which allows users to subscribe
> their interesting name service status. After tipc supports namespace,
> one dedicated tipc stack instance is created for each namespace, and
> each instance can be deemed as one independent TIPC node. As a result,
> subscriber server must be built for each namespace.
>
> Signed-off-by: Ying Xue <ying.xue@windriver.com>
> Tested-by: Tero Aho <Tero.Aho@coriant.com>
> Reviewed-by: Jon Maloy <jon.maloy@ericsson.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>
> which prevents a netns being removed if I enable TIPC.
>
> I am not familiar with TIPC code, please take a look.
>
Thank you for the report! I will investigate it, so please wait a moment.
Regards,
Ying
> Thanks!
>
>
prev parent reply other threads:[~2015-03-09 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 23:29 netns refcount leak Cong Wang
2015-03-09 9:50 ` Ying Xue [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=54FD6CE4.5040708@windriver.com \
--to=ying.xue@windriver.com \
--cc=cwang@twopensource.com \
--cc=netdev@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.