2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2007-02-09 23:25:21 +09:00
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
2014-12-02 15:00:24 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2006-01-11 13:30:43 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2006-01-11 13:30:43 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2006-01-11 13:30:43 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2015-02-09 09:50:18 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:07 +08:00
|
|
|
|
2015-02-09 09:50:18 +01:00
|
|
|
|
2015-11-19 14:30:42 -05:00
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2011-05-30 09:44:38 -04:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2006-03-20 22:37:04 -08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2012-08-16 12:09:11 +00:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2006-07-21 14:51:30 -07:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-03-20 22:36:47 -08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2007-02-09 23:25:21 +09:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-03-20 22:36:47 -08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2012-07-10 10:55:09 +00:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2007-02-09 23:25:21 +09:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2006-03-20 22:36:47 -08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:43 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:10 +08:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:43 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:43 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-15 16:48:53 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2012-04-30 15:29:02 -04:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-30 10:48:48 -04:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-02-15 10:40:46 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2016-02-02 10:52:10 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-02 10:52:10 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-02-15 10:40:48 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2006-03-20 22:36:47 -08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-15 16:48:51 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2012-06-29 00:16:37 -04:00
|
|
|
|
2006-03-20 22:36:47 -08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-03-20 22:36:47 -08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2018-03-29 23:20:43 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2018-04-17 21:25:42 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-03-20 22:36:47 -08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-17 21:25:42 +02:00
|
|
|
|
|
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2018-04-17 21:25:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:26 +08:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2012-07-10 10:55:09 +00:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
2011-11-07 17:00:54 -05:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
tipc: allow closest-first lookup algorithm when legacy address is configured
The removal of an internal structure of the node address has an unwanted
side effect.
- Currently, if a user is sending an anycast message with destination
domain 0, the tipc_namebl_translate() function will use the 'closest-
first' algorithm to first look for a node local destination, and only
when no such is found, will it resort to the cluster global 'round-
robin' lookup algorithm.
- Current users can get around this, and enforce unconditional use of
global round-robin by indicating a destination as Z.0.0 or Z.C.0.
- This option disappears when we make the node address flat, since the
lookup algorithm has no way of recognizing this case. So, as long as
there are node local destinations, the algorithm will always select
one of those, and there is nothing the sender can do to change this.
We solve this by eliminating the 'closest-first' option, which was never
a good idea anyway, for non-legacy users, but only for those. To
distinguish between legacy users and non-legacy users we introduce a new
flag 'legacy_addr_format' in struct tipc_core, to be set when the user
configures a legacy-style Z.C.N node address. Hence, when a legacy user
indicates a zero lookup domain 'closest-first' is selected, and in all
other cases we use 'round-robin'.
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>
2018-03-22 20:42:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
2011-11-07 17:00:54 -05:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-12-02 15:00:26 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-30 10:48:48 -04:00
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-03-15 16:48:53 +01:00
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2011-05-30 10:48:48 -04:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2018-03-29 23:20:42 +02:00
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2018-01-08 21:03:30 +01:00
|
|
|
|
2017-10-13 11:04:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:28 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:28 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-15 16:48:53 +01:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2018-01-08 21:03:30 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-01-08 21:03:30 +01:00
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
2008-07-14 22:45:33 -07:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2017-01-18 13:50:51 -05:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2017-01-18 13:50:51 -05:00
|
|
|
|
|
|
|
|
|
2018-01-12 20:56:50 +01:00
|
|
|
|
2017-01-18 13:50:51 -05:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-18 13:50:51 -05:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2017-01-18 13:50:51 -05:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-18 13:50:51 -05:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2017-01-18 13:50:51 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-08 21:03:30 +01:00
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-01-08 21:03:30 +01:00
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
tipc: introduce communication groups
As a preparation for introducing flow control for multicast and datagram
messaging we need a more strictly defined framework than we have now. A
socket must be able keep track of exactly how many and which other
sockets it is allowed to communicate with at any moment, and keep the
necessary state for those.
We therefore introduce a new concept we have named Communication Group.
Sockets can join a group via a new setsockopt() call TIPC_GROUP_JOIN.
The call takes four parameters: 'type' serves as group identifier,
'instance' serves as an logical member identifier, and 'scope' indicates
the visibility of the group (node/cluster/zone). Finally, 'flags' makes
it possible to set certain properties for the member. For now, there is
only one flag, indicating if the creator of the socket wants to receive
a copy of broadcast or multicast messages it is sending via the socket,
and if wants to be eligible as destination for its own anycasts.
A group is closed, i.e., sockets which have not joined a group will
not be able to send messages to or receive messages from members of
the group, and vice versa.
Any member of a group can send multicast ('group broadcast') messages
to all group members, optionally including itself, using the primitive
send(). The messages are received via the recvmsg() primitive. A socket
can only be member of one group at a time.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-10-13 11:04:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2015-01-09 15:27:05 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2015-01-09 15:27:05 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-09 14:22:52 -05:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2014-04-28 18:00:10 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-03-29 23:20:43 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:28 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-03-29 23:20:43 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:28 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-03-29 23:20:43 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2014-12-02 15:00:28 +08:00
|
|
|
|
|
|
|
|
|
2015-11-19 14:30:42 -05:00
|
|
|
|
2014-12-02 15:00:28 +08:00
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-18 00:38:21 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-04-11 22:52:09 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-02-15 10:40:49 +01:00
|
|
|
|
2018-02-15 10:40:46 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-04-11 22:52:09 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-02-09 23:25:21 +09:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-04-11 22:52:09 +02:00
|
|
|
|
2007-02-09 23:25:21 +09:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2018-04-11 22:52:09 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-18 00:38:21 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-02-15 10:40:46 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-02-15 10:40:49 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-02-15 10:40:46 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-02-09 23:25:21 +09:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:24 +08:00
|
|
|
|
|
|
|
|
|
2018-07-27 17:28:25 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:24 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-12-02 15:00:24 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
tipc: eliminate message disordering during binding table update
We have seen the following race scenario:
1) named_distribute() builds a "bulk" message, containing a PUBLISH
item for a certain publication. This is based on the contents of
the binding tables's 'cluster_scope' list.
2) tipc_named_withdraw() removes the same publication from the list,
bulds a WITHDRAW message and distributes it to all cluster nodes.
3) tipc_named_node_up(), which was calling named_distribute(), sends
out the bulk message built under 1)
4) The WITHDRAW message arrives at the just detected node, finds
no corresponding publication, and is dropped.
5) The PUBLISH item arrives at the same node, is added to its binding
table, and remains there forever.
This arrival disordering was earlier taken care of by the backlog queue,
originally added for a different purpose, which was removed in the
commit referred to below, but we now need a different solution.
In this commit, we replace the rcu lock protecting the 'cluster_scope'
list with a regular RW lock which comprises even the sending of the
bulk message. This both guarantees both the list integrity and the
message sending order. We will later add a commit which cleans up
this code further.
Note that this commit needs recently added commit d3092b2efca1 ("tipc:
fix unsafe rcu locking when accessing publication list") to apply
cleanly.
Fixes: 37922ea4a310 ("tipc: permit overlapping service ranges in name table")
Reported-by: Tuong Lien Tong <tuong.t.lien@dektech.com.au>
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>
2018-10-19 19:55:40 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-06 14:40:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-03-06 14:40:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-03-06 14:40:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2018-04-17 21:25:42 +02:00
|
|
|
|
2014-03-06 14:40:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2018-04-17 21:25:42 +02:00
|
|
|
|
2018-05-09 02:59:41 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2018-04-17 21:25:42 +02:00
|
|
|
|
|
|
|
|
|
2014-03-06 14:40:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-06 14:40:20 +01:00
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
|
|
2014-03-06 14:40:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2012-08-16 12:09:11 +00:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2012-07-11 17:35:01 -04:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-06 14:40:20 +01:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2015-01-09 15:27:09 +08:00
|
|
|
|
2014-12-02 15:00:24 +08:00
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2014-11-24 11:10:29 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2015-02-09 09:50:03 +01:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-26 11:13:06 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-26 11:13:06 +02:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-15 16:48:55 +01:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2019-04-09 14:59:24 +07:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
|
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-02 15:00:30 +08:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-29 23:20:41 +02:00
|
|
|
|
2014-11-20 10:29:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-05 08:36:43 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2018-08-27 09:32:26 +08:00
|
|
|
|
|
|
|
|
|
2015-02-05 08:36:43 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-27 09:32:26 +08:00
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-02-05 08:36:43 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2015-02-05 08:36:43 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2015-02-05 08:36:43 -05:00
|
|
|
|
2017-10-13 11:04:22 +02:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2015-02-05 08:36:43 -05:00
|
|
|
|
2017-01-03 10:55:10 -05:00
|
|
|
|
2015-02-05 08:36:43 -05:00
|
|
|
|