[strongSwan] Deadlocked strongswan.

[Guru Shetty]

On 7 November 2013 01:05, Tobias Brunner <tobias at strongswan.org> wrote:

> Hi Guru,
>
> Thanks for the detailed report.  It is in fact a deadlock caused by
> thread 3 holding the lock in bus.c and trying to acquire the lock in
> trap_manager.c that is currently being held by thread 14, which in turn
> wants to acquire the lock in bus.c held by thread 3.
>
> This situation may occur if "ipsec route" is called (maybe via starter
> due to auto=route) while SAs are concurrently being established.
>
> The main problem is that the write lock in trap_manager.c is held while
> the IPsec policies are installed.  I pushed a fix to the trap-deadlock
> branch in our repository [1] (it won't apply to 5.0.4 directly as there
> were some changes to trap_manager.c since then).
>
> Regards,
> Tobias
>
> [1] http://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=4ffa72f65
>

Thanks much for the quick patch. I did a back port to 5.0.4. I have hit
this bug a couple of times in the last few weeks. So, I will know if this
patch helps soon.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/users/attachments/20131111/ff5d35cd/attachment.html>