Bug 2037333

Summary:	FAIL for missing -D_FORTIFY_SOURCE=2 appears to be bogus
Product:	Red Hat Enterprise Linux 9	Reporter:	Jindrich Novy <jnovy>
Component:	annobin	Assignee:	Nick Clifton <nickc>
Status:	CLOSED ERRATA	QA Contact:	Václav Kadlčík <vkadlcik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	fweimer, mcermak, nickc, skolosov, vkadlcik
Target Milestone:	rc	Keywords:	Bugfix, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	annobin-10.44-1.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 12:33:28 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:

Comment 1 Nick Clifton 2022-01-05 15:22:34 UTC

The erroneous FAIL messages are caused because the executables are being linked with the static C library (libc.a) rather than the dynamic C library (libc.so).  As a result glibc code is brought in to the executable, and glibc compiles its code without -D_FORTIFY_SOURCE=2.  Annocheck does contain heuristics to detect this static glibc code, based upon the names of the functions being called, but this method is sensitive to code reorganizations by the compiler (and linker).  In this case it turns out that some new function names are being detected, ones that were not known to the heuristic.

I have a local patch which updates annocheck's internal list of known glibc functions.  Once the permissions are in place I will build a new release.

Comment 2 Nick Clifton 2022-01-06 12:13:44 UTC

Fixed in annobin-10.42-1.el9

Comment 10 Nick Clifton 2022-01-07 15:15:24 UTC

Fixed in annobin-10.44-1.el9

Comment 18 errata-xmlrpc 2022-05-17 12:33:28 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 (new packages: annobin), 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-2022:2342