-
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 by ajstephens
-
the following invalid code causes kernel panic in jaunty 100%
tipc-config is
[ 16.698280] TIPC: Activated (version 1.7.6 compiled Jul 30 2009 15:48:42)
[ 16.698391] TIPC: Started in single node mode
[ 16.702489] TIPC: Started in network mode
[ 16.702494] TIPC: Own node address , network identity 4711
[ 16.707055] TIPC: Enabled bearer , discovery domain ,
2009-08-07 16:40:43 UTC by tonyhardie
-
Laser [gotolaser@gmail.com] has determined that VxWorks TIPC 1.7 does not support Ethernet VLAN interfaces, unlike Linux TIPC 1.7.
Laser has created a prototype patch for TIPC 1.7.6 which seems to provide this functionality (at least on VxWorks 6.3). Al has provided feedback (see below) that describes how the patch might be improved.
> - I'm not an expert in how VLAN code works in VxWorks,
2009-06-02 20:15:41 UTC by ajstephens
-
Jon, Allan,
We were also thinking that breaking the connection should be the last resort and that it would be better to retry sending any of the event messages that couldn't be sent after sleeping for some time, but I like Jon's second approach even better. In any event, I'll raise a new item on the TIPC bug tracker.
Felix
-----Original Message-----
From: Jon Maloy...
2009-05-11 15:08:40 UTC by nobody
-
ajstephens added the tipc-vxworks-1.7.6b.zip file.
2009-04-29 15:17:28 UTC by ajstephens
-
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
2009-03-18 18:48:04 UTC by sf-robot
-
ajstephens added the tipc-vxworks-1.7.6a.zip file.
2009-02-25 16:17:20 UTC by ajstephens
-
ajstephens added the tipc-1.7.5+tipcdump.patch file.
2009-02-02 15:20:49 UTC by ajstephens
-
ajstephens created the tipcdump_patch file release.
2009-02-02 15:17:22 UTC by ajstephens
-
There are several places where TIPC 1.7.6 socket routines return misleading error codes.
a) Certain routines return ERESTARTSYS if a socket operation is prematurely terminated by a signal. These routines should really return EINTR, since ERESTARTSYS is supposed to be an internal Linux error code that is not passed on to applications.
b) The connect() routine returns EISCONN in some cases...
2009-01-16 15:54:26 UTC by ajstephens
