fixes chan_iax2 race condition

There is code in chan_iax2.c that attempts to guarantee that only a single
active thread will handle a call number at a time.  This code works once
the thread is added to an active_list of threads, but we are not currently
guaranteed that a newly activated thread will enter the active_list immediately
because it is left up to the thread to add itself after frames have been
queued to it.  This means that if two frames come in for the same call number
at the same time, it is possible for them to grab two separate threads because
the first thread did not add itself to the active_list fast enough.  This
causes some pretty complex problems.

This patch resolves this race condition by immediately adding an activated
thread to the active_list within the network thread and only depending on
the thread to remove itself once it is done processing the frames queued to
it.  By doing this we are guaranteed that if another frame for the same call
number comes in at the same time, that this thread will immediately be found
in the active_list of threads.

Review: https://reviewboard.asterisk.org/r/720/



git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@270866 f38db490-d61c-443f-a65b-d21fe96a405b

0 files changed, 0 insertions, 0 deletions