[radvd-devel-l] radvd crash with multiple interfaces when 1 interface comes back up

Pekka Savola pekkas at netcore.fi
Thu May 6 00:40:00 EDT 2010

On Wed, 5 May 2010, Reuben Hawkins wrote:
> This is happening in the latest from CVS in the timer code?  Can you reproduce this crash in the code I submitted which removes the
> timers?  It seems like the timers are the source of half the problems submitted to the mailing list.  I stand by removing the
> timers.  Building a poll/select based solution will dramatically simplify the code and debugging.  Please let me know what
> guidelines I should follow to get my code integrated into the next version...

Yes, this happens with the latest CVS.  I have not tried reproducing 
with polling based mechanism, but I don't think it would exist there.

I agree that timers are causing problems (and likely continue to do 
so), and we would be better off without them, or by implementing 
better locking when using them (anyone interested in looking at 

In order for select/poll-based mechanism to be considered, it would 
need to support all MUSTs from the spec and preferably SHOULDs also. I 
recall there was some discussion about this late last year, e.g. 
relating to random delay feature.

Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

More information about the radvd-devel-l mailing list