Bug 1457172

Summary: rpcbind crash on start [rhel-7.3.z]
Product: Red Hat Enterprise Linux 7 Reporter: Jaroslav Reznik <jreznik>
Component: rpcbindAssignee: Steve Dickson <steved>
Status: CLOSED ERRATA QA Contact: Yongcheng Yang <yoyang>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.3CC: afeldt, ajb, andrew2.hart, calum.mackay, cperry, cww, darren.miller, dkholia, dmaziuk, dmoppert, dwysocha, eguan, fsorenso, jiyin, knweiss, lkimlick, m.camen, michiel.dewilde, mjtrangoni, nrm, olchansk, pasik, renaud.haxaire, riehecky, rmj, steved, swhiteho, tbecker, toracat, voetelink, vs, vuiis-sysadmin, xzhou, yoyang, zpytela
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: rpcbind-0.2.0-38.el7_3.1 Doc Type: Bug Fix
Doc Text:
Cause: Static memory was being freed do to a bug in the fix for CVE-2017-8779 Consequence: Rpcbind would die on start up do to a segmentation fault Fix: Remove code that was needlessly do the freeing of static memory Result: rpcbind now starts up cleanly
Story Points: ---
Clone Of: 1454876 Environment:
Last Closed: 2017-06-13 15:34:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1454876    
Bug Blocks:    

Description Jaroslav Reznik 2017-05-31 09:00:54 UTC
This bug has been copied from bug #1454876 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 6 VUIIS SysAdmin 2017-06-01 16:36:02 UTC
When will rpcbind-0.2.0-38.el7_3.1 be available in the update stream?

Comment 7 Yongcheng Yang 2017-06-02 04:07:09 UTC
Moving to VERIFIED according to Comment #4.

Other regression tests are in progress now.

Comment 10 errata-xmlrpc 2017-06-13 15:34:33 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.