[ofa-general] [BUG report / PATCH] fix race in the core multicast management

[Sean Hefty]

> Now, is this case there was --no-- previous event, when the port was 
> brought back online there was PORT_ACTIVE event (its a driver issue 
> which we look at). However, from the view point of the SA there was "GID 
> out" event, so the HCA port was dropped out from the multicast group and 
> the multicast routing (spanning tree, MFTs configuration etc) was 
> computed without this port being included. This is the ipoib logging of 
> what happens from its perspective (I have added the event number to the 
> "port state change event" print):

Do you know why there wasn't some sort of port down event?

>> node 1 <-> switch A <-> switch B <-> switch C <-> SA
> 
> The host would only see port up/down events as of changes in the link 
> state in the local port or in the port which is connected to it through 
> the cable.


So, if you brought the link down/up between switches A & B, node 1 
wouldn't receive any events, but it would be removed from the multicast 
group?

- Sean