[asterisk-bugs] [Asterisk 0018862]: Free parking slot logic broken if randomising start - stops early and doesn't recognize it failed (#16428 is not complete fix)

Asterisk Bug Tracker noreply at bugs.digium.com
Wed May 18 13:45:50 CDT 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18862 
====================================================================== 
Reported By:                davidw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18862
Category:                   Features/Parking
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-3156 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 307231 
Request Review:              
====================================================================== 
Date Submitted:             2011-02-21 12:52 CST
Last Modified:              2011-05-18 13:45 CDT
====================================================================== 
Summary:                    Free parking slot logic broken if randomising start 
- stops early and doesn't recognize it failed
(https://issues.asterisk.org/view.php?id=16428 is not complete fix)
Description: 
https://issues.asterisk.org/view.php?id=16428 fixes a bug relating to the exit
conditions for the free parking
slot search, but only does so if the start of the search is not randomised
(R option on ParkAndAnnounce()).

It stops the search when it hits the end of the range, not when it has
wrapped back to the starting point.

The subsequent code only properly handles the no free slot case when it
stops after going right round.  I haven't followed through, but I think
there is a potential crash downstream.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016428 [patch] park() function takes 100% of CPU
====================================================================== 

---------------------------------------------------------------------- 
 (0135109) jrose (manager) - 2011-05-18 13:45
 https://issues.asterisk.org/view.php?id=18862#c135109 
---------------------------------------------------------------------- 
Using the R option seems to break the thing entirely actually.  I set a
parkinglot with 3 slots ranging from 301-303 and when I'd use park(,,,,R)
to park myself, I'd get parked on a myriad of random numbers from 0 - 50. 
Very weird.  This is in 1.8 though if that makes any difference (probably
not)

On the other hand, I had no problem parking at 2 and then parking again
while keeping that alive and getting 1 or 0, so I don't think wrap around
is going to cause it to skip over numbers when we do get it back to working
properly. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-18 13:45 jrose          Note Added: 0135109                          
======================================================================




More information about the asterisk-bugs mailing list