A TIPC 1.7 link endpoint does not always processing incoming messages in sequential order if its bearer utilizes a driver with multiple receiving threads. This can be illustrated by the following sequence of events, involving a node with multi-core CPUs A and B:
cpu A
1) invokes tipc_recv_msg() with packet N
2) performs read_lock_bh(&tipc_net_lock) [this ensures TIPC's view of the network...
2009-08-25 17:20:50 UTC in TIPC: Cluster Communication Protocol
