100% cpu usage with unresolved name server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
socat (Debian) |
Fix Released
|
Unknown
|
|||
socat (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Description: Ubuntu 15.10
Release: 15.10
Package Info:
==========
socat:
Installed: 1.7.3.0-1
Candidate: 1.7.3.0-1
Version table:
*** 1.7.3.0-1 0
500 http://
100 /var/lib/
[Impact]
At Ubuntu Wily OS, when we use the socat with a nameserver which is not defined at /etc/hosts and is unknown, the system hits 100% cpu usage. Additional, to terminate the process you must give -9 parameter in kill command. Ctrl+C does not terminate the process.
With older versions of socat (< 1.7.3.0 upstream) the system does not drive up to 100% cpu usage, but prints appropriate error message.
[Test case]
* A simple test to validate the issue, is to execute the below command:
socat tcp:server-
* Using older version of socat the above command will print:
socat[2756] E getaddrinfo(
[Regression Potential]
This bug affects the releases that use socat 1.7.3.0 upstream version (Wily, Xenial). The Vivid, Trusty and Precise are not affected.
Changed in socat (Debian): | |
status: | Unknown → New |
Changed in socat (Debian): | |
status: | New → Fix Released |
Lefteris, could you add the upstream patch here and follow all the SRU steps? Thank you!