Comment 1 for bug 571612

Any update on this? It's been 8 months since found and reported. Any info would be great as it is a real pain!

Anyone who uses link aggregation (me), bridging, and vlans are affect due to the time required to bring up the network after reboot. Corosync comes up and dlm segfaults (something to do with network not actually being completely started?). I want a node to be able to completely recover after being fenced or the like and with this problem it won't start all it's resources again due to the segfault without restarting corosync.

I believe it is fixed in the 3.0.12 which is in Maverick - maybe this could be backported?
Or the above referenced patch...

I can figure out how to apply the patch myself but I would rather stay in sync with the HA packages...