[radvd-devel-l] reload_config in another place
Pekka Savola
pekkas at netcore.fi
Mon Dec 21 15:24:22 EST 2009
On Thu, 17 Dec 2009, LiKai wrote:
> I observed that version 1.5 has fixed an infinite loop problem
> caused by reload_config() and timer list corruption.
>
> Besides send_ra(), I saw reload_config() is also called in another
> place. Actually, it is in the loop of main() after sighup is received.
> I suspect this piece of code has similiar problem when interacted
> with timer_handler() -> set_timer().
>
> Maybe I will do a test to see if this is a real problem, when I
> get free. Or anyone can please stop me by pointing out my fault.
>
> B.R.
> Victor
Please, if you have time, do take a look at this! Much appreciated.
If this needs to be fixed, and we already have the flexible options
patch, we might have enough material for the next release.
--
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