Re: [Tipc-discussion] Yet another version checked in

[Jon M. <jon...@er...>]

The last thing I did before the port_lock changes was to add
a device notifier in eth_media, and a "tipc_block_bearer()"
function to handle this. I tested this with an  "ifconfig eth1 down/up" 
(I run dual links most of the time) during traffic, and this worked
fine, but when I thereafter removed the module  I got a crash
in bcast.c/blink_remove(), - a NULL pointer access. 

I corrected this (I believed) and tested it, but it seems like I 
have still introduced some problem here. 

Maybe Guo or Ling can say more about this ? Pay special
attention to the flag "blocked" in the bearer, if this gets stuck with
 with the wrong value the traffic will never restart. 

/Jon

Daniel McNeil wrote:


On Tue, 2004-05-18 at 17:19, Jon Maloy wrote:

  

I think I have succeeded in making the port/transport level lock

handling somewhat easier to understand, without changing the

basic locking policy.



    



I was testing multicast and Mark had updated 2 of the machines to 

use the latest tipc cvs and multicast sendto()s were not being

seen by a process on one of the nodes running the latest version.



I changed the tipc version on the node whose messages were not

being seen to Monday's checked in version.  (2 nodes running

monday's version and 1 running latest) the multicast sends

are correctly seen by all processes on all nodes.



Something is not quite right.  Any ideas?



Daniel