[asterisk-bugs] [Asterisk 0011535]: [patch] chan_sip can cause 100% CPU usage on illegal listening IP

[noreply at bugs.digium.com]

The following issue has been ASSIGNED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11535 
====================================================================== 
Reported By:                one47
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   11535
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.15  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-13-2007 06:56 CST
Last Modified:              01-04-2008 13:18 CST
====================================================================== 
Summary:                    [patch] chan_sip can cause 100% CPU usage on illegal
listening IP
Description: 
When using "-p" realtime priority, this will kill the server!

It is unlikely to happen, but is totally reproducable here on both 1.2 and
1.4 systems. Set in sip.conf a valid IP configuration, eg:
  [general]
  port = 5060
  bindaddr = 10.0.0.16
and restart asterisk. This registers the FD with asterisk core-io OK. Now
change it to an "illegal" IP address that you know will fail, eg:
  [general]
  port = 5060
  bindaddr = 10.0.0.17
SIP notices that it cannot use this anymore, but fail to deregister the
fact with asterisk's core-io list, so the io being carried out on
chan_sip's behalf fails, and logs an error message every few milliseconds.

When running in high priority mode, this wipes out the box. When not in
high priority mode, a major stream of errors is output, which is quite
inconvenient!
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-04-08 13:18  Corydon76      Status                   new => assigned     
01-04-08 13:18  Corydon76      Assigned To               => Corydon76       
======================================================================