1. 25 2月, 2012 3 次提交
    • A
      tipc: Remove duplicate check of message destination node · c74a4611
      Allan Stephens 提交于
      Eliminates a check in the processing of TIPC messages arriving from
      off node that ensures the message is destined for this node, since this
      check duplicates an earlier check. (The check would be necessary if TIPC
      needed to be able to route incoming messages to another node, but the
      elimination of multi-cluster support means that this never happens and
      all incoming messages are consumed by the receiving node.)
      
      Note: This change involves the elimination of a single "if" statement
      with a large "then" clause; consequently, a significant number of lines
      end up getting re-indented. In addition, a simple message header access
      routine that is no longer referenced is eliminated. However, the only
      functional change is the elimination of the single check described above.
      Signed-off-by: NAllan Stephens <allan.stephens@windriver.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      c74a4611
    • A
      tipc: Detect duplicate nodes using different network interfaces · 97878a40
      Allan Stephens 提交于
      Utilizes the new "node signature" field in neighbor discovery messages
      to ensure that all links TIPC associates with a given <Z.C.N> network
      address belong to the same neighboring node. (Previously, TIPC could not
      tell if link setup requests arriving on different interfaces were from
      the same node or from two different nodes that has mistakenly been assigned
      the same network address.)
      
      The revised algorithm for detecting a duplicate node considers both the
      node signature and the network interface adddress specified in a request
      message when deciding how to respond to a link setup request. This prevents
      false alarms that might otherwise arise during normal network operation
      under the following scenarios:
      
      a) A neighboring node reboots. (The node's signature changes, but the
      network interface address remains unchanged.)
      
      b) A neighboring node's network interface is replaced. (The node's signature
      remains unchanged, but the network interface address changes.)
      
      c) A neighboring node is completely replaced. (The node's signature and
      network interface address both change.)
      
      The algorithm also handles cases in which a node reboots and re-establishes
      its links to TIPC (or begins re-establishing those links) before TIPC
      detects that it is using a new node signature. In such cases of "delayed
      rediscovery" TIPC simply accepts the new signature without disrupting
      communication that is already underway over the links.
      
      Thanks to Laser [gotolaser@gmail.com] for his contributions to the
      development of this enhancement.
      Signed-off-by: NAllan Stephens <allan.stephens@windriver.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      97878a40
    • A
      tipc: Introduce node signature field in neighbor discovery message · fc0eea69
      Allan Stephens 提交于
      Adds support for the new "node signature" in neighbor discovery messages,
      which is a 16 bit identifier chosen randomly when TIPC is initialized.
      This field makes it possible for nodes receiving a neighbor discovery
      message to detect if multiple neighboring nodes are using the same network
      address (i.e. <Z.C.N>), even when the messages are arriving on different
      interfaces.
      
      This first phase of node signature support creates the signature,
      incorporates it into outgoing neighbor discovery messages, and tracks
      the signature used by valid neighbors. An upcoming patch builds on this
      foundation to implement the improved duplicate neighbor detection checking.
      Signed-off-by: NAllan Stephens <allan.stephens@windriver.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      fc0eea69
  2. 24 2月, 2012 1 次提交
  3. 23 2月, 2012 2 次提交
  4. 22 2月, 2012 5 次提交
  5. 18 2月, 2012 1 次提交
  6. 17 2月, 2012 10 次提交
  7. 16 2月, 2012 5 次提交
  8. 15 2月, 2012 12 次提交
  9. 14 2月, 2012 1 次提交