From: Ying Xue <ying.xue@windriver.com>
To: <davem@davemloft.net>
Cc: jon.maloy@ericsson.com, cwang@twopensource.com,
tipc-discussion@lists.sourceforge.net, netdev@vger.kernel.org
Subject: [PATCH net-next 0/3] tipc: fix netns refcnt leak
Date: Wed, 18 Mar 2015 09:32:56 +0800 [thread overview]
Message-ID: <1426642379-20503-1-git-send-email-ying.xue@windriver.com> (raw)
The series aims to eliminate the issue of netns refcount leak. But
during fixing it, another two additional problems are found. So all
of known issues associated with the netns refcnt leak are resolved
at the same time in the patchset.
Ying Xue (3):
tipc: fix netns refcnt leak
tipc: fix a potential deadlock when nametable is purged
tipc: withdraw tipc topology server name when namespace is deleted
net/tipc/name_table.c | 4 +--
net/tipc/server.c | 47 ++++++++++++++++++++++++----
net/tipc/socket.c | 83 +------------------------------------------------
net/tipc/socket.h | 4 ---
4 files changed, 44 insertions(+), 94 deletions(-)
--
1.7.9.5
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
next reply other threads:[~2015-03-18 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 1:32 Ying Xue [this message]
2015-03-18 1:32 ` [PATCH net-next 1/3] tipc: fix netns refcnt leak Ying Xue
2015-03-18 1:32 ` [PATCH net-next 2/3] tipc: fix a potential deadlock when nametable is purged Ying Xue
2015-03-18 1:32 ` [PATCH net-next 3/3] tipc: withdraw tipc topology server name when namespace is deleted Ying Xue
2015-03-18 2:12 ` [PATCH net-next 0/3] tipc: fix netns refcnt leak David Miller
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=1426642379-20503-1-git-send-email-ying.xue@windriver.com \
--to=ying.xue@windriver.com \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
/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).