Bug 1437618

Summary: Fix for thread cancellation of IdM functions incorrect in rhel-6.9.
Product: Red Hat Enterprise Linux 6 Reporter: Jaroslav Reznik <jreznik>
Component: glibcAssignee: Carlos O'Donell <codonell>
Status: CLOSED ERRATA QA Contact: Sergey Kolosov <skolosov>
Severity: high Docs Contact: Lucie Vařáková <lmanasko>
Priority: urgent    
Version: 6.9CC: ashankar, bgollahe, codonell, fdanapfe, fweimer, jreznik, lmanasko, manjunath.b.patil, mcermak, mnewsome, mpoole, pfrankli, salmy, skolosov, thomas.oulevey
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: glibc-2.12-1.209.el6_9.1 Doc Type: Bug Fix
Doc Text:
A defect in thread-cancellation support for the setmntent() function could cause the function to fail and return an error where it was expected to succeed. Consequently, programs that rely on setmntent() could fail to start. The setmntent() function has been fixed, and now works as expected. In addition, the setttyent() and setnetgrent() functions, and all APIs that rely on the /etc/hosts.conf file, have been enhanced to provide improved support for thread cancellation.
Story Points: ---
Clone Of: 1437147 Environment:
Last Closed: 2017-04-11 11:49:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1437147    
Bug Blocks:    

Description Jaroslav Reznik 2017-03-30 16:46:31 UTC
This bug has been copied from bug #1437147 and has been proposed
to be backported to 6.9 z-stream (EUS).

Comment 5 Carlos O'Donell 2017-03-31 01:22:47 UTC
*** Bug 1437706 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2017-04-11 11:49:58 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-2017:0894