[asterisk-dev] Bug/patch 9596

Michiel van Baak michiel at vanbaak.info
Fri Jun 1 15:33:48 MST 2007

On 15:21, Fri 01 Jun 07, Dan Austin wrote:
> That won't cause any problems.  The variable in question
> is in the device structure, so it is unique per device.
> The issue is that it is possible that skinny_ss wakes up
> and tries to read the variable at the same time the user
> enters a new digit.  The window is small, but possible.
> I am not sure what the failure mode would be.

Yeah, after reading the code again I noticed this as well.

I'm running this on my home system and have had like 12
calls this evening and nothing went wrong at all.
I dont have anything with more traffic so I'm not able to
test what the mode would be neither.

> I am familiar with the reasons and concepts for locking,
> but not with the implementation.  

same here. Trying to learn more about it now. not only for
asterisk but for my whole C skillz.


Michiel van Baak
michiel at vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD

"Why is it drug addicts and computer afficionados are both called users?"

More information about the asterisk-dev mailing list