Bug 1712296

Summary: [RHEL-7.7] segfault at 0 ip 0000000000404c8a sp 00007fff6b4eb540 error 4 in ibacm[400000+d000]
Product: Red Hat Enterprise Linux 7 Reporter: zguo <zguo>
Component: rdma-coreAssignee: Jarod Wilson <jarod>
Status: CLOSED ERRATA QA Contact: zguo <zguo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.7CC: honli, kheib, rdma-dev-team, tborcin
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rdma-core-22.4-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-31 20:11:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description zguo 2019-05-21 09:40:19 UTC 
Description of problem:

Caught segfault at 0 ip 0000000000404c8a sp 00007fff6b4eb540 error 4 in ibacm[400000+d000] when running ibacm testing

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:

cxgb4 t6 iw: https://beaker.engineering.redhat.com/jobs/3549682
cxgb3 t3 iw: https://beaker.engineering.redhat.com/jobs/3549686
bnxt_re roce: https://beaker.engineering.redhat.com/recipes/6872879#task92851222

Actual results:

https://beaker.engineering.redhat.com/recipes/6890698/tasks/93145810/results/427406344/logs/console_dmesg--kernel-infiniband-ibacm-client.log

Expected results:

No segfault

Additional info:
It's reproducible on RHEL-7.6. 
PASS on IB(mlx5, qib, hfi1) devices
Comment 14 Jarod Wilson 2019-12-03 19:24:36 UTC 
Okay, vacation time made my brain melt, apparently. This is NOT yet pushed to dist-git, but is an easy fix (simple upstream backport), locally committed and built already. We just need an exception flag to be able to push it.
Comment 18 errata-xmlrpc 2020-03-31 20:11:37 UTC 
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-2020:1192