Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1589866 - [OVS] [qede] OVS daemon got segfault while repeatedly configuring OVS-dpdk bridge
[OVS] [qede] OVS daemon got segfault while repeatedly configuring OVS-dpdk br...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openvswitch (Show other bugs)
7.5
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Timothy Redaelli
ovs-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-06-11 10:50 EDT by Jean-Tsung Hsiao
Modified: 2018-06-21 09:36 EDT (History)
5 users (show)

See Also:
Fixed In Version: openvswitch-2.9.0-46.el7fdn
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-21 09:36:37 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 Product Errata RHBA-2018:1962 None None None 2018-06-21 09:36 EDT

  None (edit)
Description Jean-Tsung Hsiao 2018-06-11 10:50:23 EDT
Description of problem: [OVS] [qede] OVS daemon got segfault while repeatedly configuring OVS-dpdk bridge

The segfault always happened at the 5th iteration of the following for loop:

for i in {1..5}; do echo Test $i; sh /home/jhsiao/ovs_loopback_qede.sh; sleep 30; ps -elf | grep ovs-vs; dmesg | grep segfault; done


Version-Release number of selected component (if applicable):
OVS 2.9.0-37 fdP
RHEL7.5

How reproducible: Reproducible


Steps to Reproduce: See above.
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 Jean-Tsung Hsiao 2018-06-18 19:53:35 EDT
The fix of this bug has been verified by OVS 2.9.0-47.
Comment 6 errata-xmlrpc 2018-06-21 09:36:37 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/RHBA-2018:1962

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