aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authortilghman <tilghman@f38db490-d61c-443f-a65b-d21fe96a405b>2008-01-27 21:59:53 +0000
committertilghman <tilghman@f38db490-d61c-443f-a65b-d21fe96a405b>2008-01-27 21:59:53 +0000
commit940f913146cc96cda9132600151d40ee85680ee6 (patch)
treea0610b66a954f2b2f98aedcd42cbc2b4250184b8 /include
parent74e414e5f2dbf490e4c2f67ce638e0ec9e4ad0ae (diff)
When deleting a task from the scheduler, ignoring the return value could
possibly cause memory to be accessed after it is freed, which causes all sorts of random memory corruption. Instead, if a deletion fails, wait a bit and try again (noting that another thread could change our taskid value). (closes issue #11386) Reported by: flujan Patches: 20080124__bug11386.diff.txt uploaded by Corydon76 (license 14) Tested by: Corydon76, flujan, stuarth` git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@100465 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'include')
-rw-r--r--include/asterisk/sched.h10
1 files changed, 10 insertions, 0 deletions
diff --git a/include/asterisk/sched.h b/include/asterisk/sched.h
index 7489c6377..84a65a07a 100644
--- a/include/asterisk/sched.h
+++ b/include/asterisk/sched.h
@@ -35,6 +35,16 @@ extern "C" {
*/
#define SCHED_MAX_CACHE 128
+#define AST_SCHED_DEL(sched, id) \
+ do { \
+ int _count = 0; \
+ while (id > -1 && ast_sched_del(sched, id) && _count++ < 10) \
+ usleep(1); \
+ if (_count == 10) \
+ ast_log(LOG_WARNING, "Unable to cancel schedule ID %d. This is probably a bug (%s: %s, line %d).\n", id, __FILE__, __PRETTY_FUNCTION__, __LINE__); \
+ id = -1; \
+ } while (0);
+
struct sched_context;
/*! \brief New schedule context