Bug 985492

Summary:	p11-kit: pthread_atfork handling
Product:	Red Hat Enterprise Linux 7	Reporter:	Florian Weimer <fweimer>
Component:	p11-kit	Assignee:	Daiki Ueno <dueno>
Status:	CLOSED ERRATA	QA Contact:	Alicja Kario <hkario>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	hkario, nmavrogi
Target Milestone:	rc
Target Release:	7.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	p11-kit-0.23.5-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 16:52:09 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:
Bug Depends On:
Bug Blocks:	983512

Description Florian Weimer 2013-07-17 15:40:05 UTC

I'm not convinced that the pthread_atfork handling is correct.  The lock underlying p11_lock() needs to be acquired before the fork and released afterwards.  Otherwise, the reinitialization in the child process can fail if the a fork happens while the p11_lock has been taken by another thread.

Comment 2 Stef Walter 2013-07-17 16:47:08 UTC

pthread_atfork() is pretty much impossible to get correct. We simply try to do what the PKCS#11 spec says. But it's pretty bogus.

But I think this is too risky to fix in the stable branch. Unless you have objections I'll change to RHEL 7.1.

Comment 5 Stef Walter 2014-08-07 07:32:25 UTC

This needs work in Fedora before updating it in RHEL, bumping to RHEL 7.2

Comment 9 errata-xmlrpc 2017-08-01 16:52:09 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/RHEA-2017:1981