Bug 2445761

Summary: mstflint 4.32 segfaults on connectx-3 pro cards
Product: [Fedora] Fedora Reporter: Ian Kumlien <ian.kumlien>
Component: mstflintAssignee: Davide Cavalca <davide>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 43CC: davide, honggangli, jiri, kheib, mschmidt, negativo17
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-07-31 15:16:59 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 Ian Kumlien 2026-03-09 13:27:54 UTC 
Description of problem:
mstflint -d 04:00.0 q
Segmentation fault         (core dumped) mstflint -d 04:00.0 q

Version-Release number of selected component (if applicable):
mstflint --version
mstflint, mstflint 4.32.0, Git SHA Hash: N/A

How reproducible:
100%

Steps to Reproduce:
1. install connectx-3 pro networkcard
2. run mstflint to query it
3. result

Actual results:
segfault

Expected results:
firmware version output

Additional info:
I dunno if 4.35 fixes things for me, i built it and installed in local but at least it didn't segfault - instead it gave me:
stflint -d 04:00.0 q                                                                                                                                                                                                           
FATAL - crspace read (0xf0014) failed: Invalid argument                                                                                                                                                                                                      
FATAL - crspace read (0xf0014) failed: Invalid argument                                                                                                                                                                                                      
-E- Cannot open Device: 04:00.0. Invalid argument. MFE_GENERAL_ERROR

(even with setenforce 0)
Comment 1 Michal Schmidt 2026-07-31 15:16:59 UTC 

*** This bug has been marked as a duplicate of bug 2445760 ***