From: David Miller <davem@davemloft.net>
To: jon.maloy@ericsson.com
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
hoang.h.le@dektech.com.au,
mohan.krishna.ghanta.krishnamurthy@ericsson.com
Subject: Re: [net-next 1/1] tipc: fix bug during lookup of multicast destination nodes
Date: Mon, 15 Jan 2018 14:27:29 -0500 (EST) [thread overview]
Message-ID: <20180115.142729.659157027252943827.davem@davemloft.net> (raw)
In-Reply-To: <1515787010-10082-1-git-send-email-jon.maloy@ericsson.com>
From: Jon Maloy <jon.maloy@ericsson.com>
Date: Fri, 12 Jan 2018 20:56:50 +0100
> In commit 232d07b74a33 ("tipc: improve groupcast scope handling") we
> inadvertently broke non-group multicast transmission when changing the
> parameter 'domain' to 'scope' in the function
> tipc_nametbl_lookup_dst_nodes(). We missed to make the corresponding
> change in the calling function, with the result that the lookup always
> fails.
>
> A closer anaysis reveals that this parameter is not needed at all.
> Non-group multicast is hard coded to use CLUSTER_SCOPE, and in the
> current implementation this will be delivered to all matching
> destinations except those which are published with NODE_SCOPE on other
> nodes. Since such publications never will be visible on the sending node
> anyway, it makes no sense to discriminate by scope at all.
>
> We now remove this parameter altogether.
>
> Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Applied, thanks Jon.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2018-01-15 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 19:56 [net-next 1/1] tipc: fix bug during lookup of multicast destination nodes Jon Maloy
2018-01-15 19:27 ` David Miller [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=20180115.142729.659157027252943827.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hoang.h.le@dektech.com.au \
--cc=jon.maloy@ericsson.com \
--cc=mohan.krishna.ghanta.krishnamurthy@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).