[Home]

Summary:ASTERISK-29445: res_calendar: Crash when checking if calendar is busy
Reporter:Ross Beer (rossbeer)Labels:
Date Opened:2021-05-22 13:25:51Date Closed:2021-08-24 09:57:49
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Resources/res_calendar
Versions:16.18.0 Frequency of
Occurrence		Occasional
Related
Issues:
Environment:CentOS 7Attachments:( 0) core-asterisk-198215-1621699368-thread1.txt
Description:Chash when refreshing calendar and checking status:

{noformat}
Thread 1 (Thread 0x2b66168c9700 (LWP 198675)):
#0  0x000000000045f330 in internal_is_ao2_object (user_data=0x6c61760000138a) at astobj2.c:203
       p = 0x6c617600001372
#1  0x0000000000461a6c in internal_ao2_traverse (self=0x6c61760000138a, flags=OBJ_NODATA, cb_fn=0x2b658789f93c <calendar_busy_callback>, arg=0x2b66168c8bac, data=0x0, type=AO2_CALLBACK_DEFAULT, tag=0x2b65878a7ca9 "", file=0x2b65878a7c9a "res_calendar.c", line=376, func=0x2b65878a9170 <__PRETTY_FUNCTION__.15897> "calendar_is_busy") at astobj2_container.c:244
       ret__LINE__ = 0
       ret = 0x0
       cb_default = 0x0
       cb_withdata = 0x0
       node = 0x63732d796164696c
       traversal_state = 0xffffffff00000143
       orig_lock = (AO2_LOCK_REQ_RDLOCK | AO2_LOCK_REQ_WRLOCK | unknown: 11104)
       multi_container = 0x0
       multi_iterator = 0x0
       __PRETTY_FUNCTION__ = "internal_ao2_traverse"
#2  0x0000000000461ff5 in __ao2_callback (c=0x6c61760000138a, flags=OBJ_NODATA, cb_fn=0x2b658789f93c <calendar_busy_callback>, arg=0x2b66168c8bac, tag=0x2b65878a7ca9 "", file=0x2b65878a7c9a "res_calendar.c", line=376, func=0x2b65878a9170 <__PRETTY_FUNCTION__.15897> "calendar_is_busy") at astobj2_container.c:414
#3  0x00002b658789fa0e in calendar_is_busy (cal=0x2b63b43923f0) at res_calendar.c:376
       is_busy = 0
       __PRETTY_FUNCTION__ = "calendar_is_busy"
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2021-05-22 13:25:52.116-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
By: Sean Bright (seanbright) 2021-08-24 09:35:36.522-0500

Attach the full backtrace, not just thread 1.
By: Ross Beer (rossbeer) 2021-08-24 09:45:21.299-0500

The full backtraces are normally sent to the dev team by email. I have just looked to see if I have any recent backtraces for this issue, but it doesn't look like I have. Sorry, but I guess it's also a good thing :)
By: Sean Bright (seanbright) 2021-08-24 09:57:49.953-0500

Feel free to re-open when you can provide a full backtrace.