soft deadlock detection bug in acquire_call

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry the diff was missing.

On Fri, Mar 25, 2011 at 9:25 PM, Attila Magyar <m.magyar3 at gmail.com> wrote:

> Hi,
>
> I've found a bug in the acquire_call function in pjsua_call.c. The problem
> is that the timeout, which is used by the deadlock detection algorithm is
> not correctly initialized.
>
> The msec is set: timeout.msec = PJSUA_ACQUIRE_CALL_TIMEOUT;
> But time.sec is not set to any value, so it can be any garbage on the
> stack. In my case it was 139889163008162sec 0msec after the normalize. So
> what is missing is just a timeout.sec = 0;
>
> regards
> Attila Magyar
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20110325/f6ac3e00/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix_deadlock_detection.diff
Type: application/octet-stream
Size: 360 bytes
Desc: not available
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20110325/f6ac3e00/attachment.diff>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux