Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1473735 - ovs-vswitchd crashes with SIGSEGV randomly when adding/removing interfaces
ovs-vswitchd crashes with SIGSEGV randomly when adding/removing interfaces
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch (Show other bugs)
10.0 (Newton)
Unspecified Unspecified
medium Severity high
: z4
: 10.0 (Newton)
Assigned To: Timothy Redaelli
Alexander Stafeyev
: Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-21 10:19 EDT by Daniel Alvarez Sanchez
Modified: 2018-06-08 06:58 EDT (History)
9 users (show)

See Also:
Fixed In Version: openvswitch-2.6.1-12.git20161206.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-09-06 12:59:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 1468334 None CLOSED neutron-openvswitch-agent crashes after SIGTERM is received and openvswitch/agent are not restarted 2018-09-17 11:40 EDT
Red Hat Bugzilla 1472832 None None None 2017-08-17 09:22 EDT
Red Hat Product Errata RHSA-2017:2648 normal SHIPPED_LIVE Moderate: openvswitch security and bug fix update 2017-09-06 16:53:24 EDT

  None (edit)
Description Daniel Alvarez Sanchez 2017-07-21 10:19:01 EDT
This bug is a follow up from bug #1468334 [0].

Through the examination of the coredump submitted to it, we concluded that getifaddrs() from glibc is returning an interface with ifa_name set to NULL.
When openvswitch tries to compare it through strncmp(), it will crash trying to access a NULL location.

I have submitted a patch to OVS master [1] which checks that ifa_name is not NULL prior to calling strncmp(). 

Versions:

glibc.x86_64                    2.17-157.el7_3.1 
kernel.x86_64                   3.10.0-514.6.1.el7

Additional info:
This's been observed in an OpenStack compute node using hybrid firewall (more interfaces) and ~70 VM's (with a total of ~400 interfaces).
It looks like this bug comes from a different bug in glibc which shouldn't
return an unnamed interface. I have filled a bug [2] but until it's confirmed/fixed I think we have to protect ourselves in OVS through [1].

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1468334
Version-Release number of selected component (if applicable):
[1] https://mail.openvswitch.org/pipermail/ovs-dev/2017-July/335859.html
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=21812
Comment 13 errata-xmlrpc 2017-09-06 12:59:49 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2648

Note You need to log in before you can comment on or make changes to this bug.