tipc: obsolete TIPC_ZONE_SCOPE
authorJon Maloy <jon.maloy@ericsson.com>
Thu, 15 Mar 2018 15:48:51 +0000 (16:48 +0100)
committerDavid S. Miller <davem@davemloft.net>
Sat, 17 Mar 2018 21:11:46 +0000 (17:11 -0400)
commit928df1880e24bcd47d6359ff86df24db3dfba3c3
treeb191aaca13f510bfd7409089d47f5346403a68e3
parent4f1aec01fcb84faf79bb6fabb82a5c850b186e03
tipc: obsolete TIPC_ZONE_SCOPE

Publications for TIPC_CLUSTER_SCOPE and TIPC_ZONE_SCOPE are in all
aspects handled the same way, both on the publishing node and on the
receiving nodes.

Despite previous ambitions to the contrary, this is never going to change,
so we take the conseqeunce of this and obsolete TIPC_ZONE_SCOPE and related
macros/functions. Whenever a user is doing a bind() or a sendmsg() attempt
using ZONE_SCOPE we translate this internally to CLUSTER_SCOPE, while we
remain compatible with users and remote nodes still using ZONE_SCOPE.

Furthermore, the non-formalized scope value 0 has always been permitted
for use during lookup, with the same meaning as ZONE_SCOPE/CLUSTER_SCOPE.
We now permit it even as binding scope, but for compatibility reasons we
choose to not change the value of TIPC_CLUSTER_SCOPE.

Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
include/uapi/linux/tipc.h
net/tipc/addr.c
net/tipc/addr.h
net/tipc/msg.c
net/tipc/name_table.c
net/tipc/net.c
net/tipc/socket.c