Bug 1506802

Summary:	glibc: Fix regression in handling of x86_64 subdirectories in the ld.so search path
Product:	[Fedora] Fedora	Reporter:	Dave Airlie <airlied>
Component:	glibc	Assignee:	Florian Weimer <fweimer>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	aoliva, arjun.is, awilliam, codonell, dj, fweimer, gmarr, law, mattdm, mfabian, pfrankli, robatino, rth, siddhesh
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	RejectedBlocker AcceptedFreezeException
Fixed In Version:	glibc-2.26-16.fc27	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-15 17:41:32 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:	1396705

Description Dave Airlie 2017-10-26 19:37:33 UTC

I attempted to run some games I had running on f25 fine, they failed to start due to not finding their libraries, I asked the vendors and they pointed me at this glibc commit.

Can we get this included in F27.

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=45ff34638f034877b6a490c217d6a0632ce263f4

Thanks,
Dave.

Comment 1 Adam Williamson 2017-10-26 20:35:55 UTC

This doesn't sound like it violates any of the criteria, so I'm -1 blocker unless more information arises. We could consider it for a freeze exception, but poking glibc late in release cycles is a bit scary. What would be the benefit to getting it in the release as opposed to a 0-day update? For people playing Steam games from live images? Is that commonly done?

Comment 2 Carlos O'Donell 2017-10-27 02:17:55 UTC

DJ,

Would you be able to look into this and verify the suggested fix?

Comment 3 Matthew Miller 2017-10-27 10:45:27 UTC

-1 Blocker, +1 FE.

I think the main risk with a zero-day is a bad impression for people who install and try to run games or other impacted without doing an update first. I don't think that's enough to block the release on, but assuming glibc team is good with the fix and we can get it in early enough that we're not needing last-minute hero-testing, it'd be nice.

Comment 4 Geoffrey Marr 2017-10-30 19:58:08 UTC

Discussed during the 2017-10-30 blocker review meeting: [1]

The decision to classify this bug as a RejectedBlocker and an AcceptedFreezeException was made as this bug doesn't violate any blocker criteria, but is bad enough to warrant a fix for release.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-10-30/f27-blocker-review.2017-10-30-16.00.txt

Comment 5 Fedora Update System 2017-11-02 11:18:44 UTC

glibc-2.26-16.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-6e4251b286

Comment 6 Fedora Update System 2017-11-04 18:02:47 UTC

glibc-2.26-16.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-6e4251b286

Comment 7 Florian Weimer 2017-11-06 14:25:30 UTC

(In reply to Fedora Update System from comment #5)
> glibc-2.26-16.fc27 has been submitted as an update to Fedora 27.
> https://bodhi.fedoraproject.org/updates/FEDORA-2017-6e4251b286

Note that this update contains only the minimal fix on top of glibc-2.26-15.fc27 to fix this bug.

Comment 8 Fedora Update System 2017-11-15 17:41:32 UTC

glibc-2.26-16.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.