| Summary: | ASTERISK-06383: [patch] chan_sip possible deadlock | ||
| Reporter: | Denis Smirnov (mithraen) | Labels: | |
| Date Opened: | 2006-02-21 05:01:29.000-0600 | Date Closed: | 2011-06-07 14:00:26 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) asterisk.mithraen.debug.deadlock.patch | |
| Description: | I have asterisk deadlock in find_call I don't know is this code have bug, but looks like is. Please, check this patch | ||
| Comments: | By: Olle Johansson (oej) 2006-02-21 13:13:44.000-0600 According to the bug guidelines you need to upload a SIP debug output when you report a bug in sip. By: Olle Johansson (oej) 2006-02-21 13:14:26.000-0600 It's very hard to judge your patch without more information... By: Denis Smirnov (mithraen) 2006-02-22 04:43:32.000-0600 Ok, I try to get sip debug. I can't reproduce this bug, only wait for it -- I see this problem rarely in production, where I can't write debug log all time. But I want to get information -- is in find_call ast_mutex_lock(&p->lock) _must_ be before ast_mutex_unlock(&iflock)? If no, that code _may_ introduce deadlocks, and must be fixed. By: Olle Johansson (oej) 2006-04-03 15:30:12 Suspended pending more information. | ||