From: Jon Maloy <jon.maloy@ericsson.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <gordan.mihaljevic@dektech.com.au>,
<tung.q.nguyen@dektech.com.au>, <hoang.h.le@dektech.com.au>,
<jon.maloy@ericsson.com>, <canh.d.luu@dektech.com.au>,
<ying.xue@windriver.com>, <tipc-discussion@lists.sourceforge.net>
Subject: [net 0/4] tipc: fixes in duplicate address discovery function
Date: Fri, 6 Jul 2018 20:10:02 +0200 [thread overview]
Message-ID: <1530900606-24429-1-git-send-email-jon.maloy@ericsson.com> (raw)
commit 25b0b9c4e835 ("tipc: handle collisions of 32-bit node address
hash values") introduced new functionality that has turned out to
contain several bugs and weaknesses.
We address those in this series.
Jon Maloy (4):
tipc: fix wrong return value from function tipc_node_try_addr()
tipc: correct discovery message handling during address trial period
tipc: fix correct setting of message type in second discoverer
tipc: make function tipc_net_finalize() thread safe
net/tipc/discover.c | 18 +++++++++++-------
net/tipc/net.c | 17 +++++++++++------
net/tipc/node.c | 7 +++++--
3 files changed, 27 insertions(+), 15 deletions(-)
--
2.1.4
next reply other threads:[~2018-07-06 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 18:10 Jon Maloy [this message]
2018-07-06 18:10 ` [net 1/4] tipc: fix wrong return value from function tipc_node_try_addr() Jon Maloy
2018-07-06 18:10 ` [net 2/4] tipc: correct discovery message handling during address trial period Jon Maloy
2018-07-06 18:10 ` [net 3/4] tipc: fix correct setting of message type in second discoverer Jon Maloy
2018-07-06 18:10 ` [net 4/4] tipc: make function tipc_net_finalize() thread safe Jon Maloy
2018-07-07 11:03 ` [net 0/4] tipc: fixes in duplicate address discovery function 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=1530900606-24429-1-git-send-email-jon.maloy@ericsson.com \
--to=jon.maloy@ericsson.com \
--cc=canh.d.luu@dektech.com.au \
--cc=davem@davemloft.net \
--cc=gordan.mihaljevic@dektech.com.au \
--cc=hoang.h.le@dektech.com.au \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.q.nguyen@dektech.com.au \
--cc=ying.xue@windriver.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).