Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 2161303

Summary: stargz-snapshotter: Update -D_FORTIFY_SOURCE to use %_fortify_level
Product: [Fedora] Fedora Reporter: Siddhesh Poyarekar <sipoyare>
Component: stargz-snapshotterAssignee: Kohei Tokunaga <ktokunaga.mail>
Status: CLOSED RAWHIDE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: go-sig, ktokunaga.mail, lsm5, rh.container.bot
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: stargz-snapshotter-0.14.2-2.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-07 16:13:43 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: 2158232    

Description Siddhesh Poyarekar 2023-01-16 15:03:43 UTC 
Description of problem:
The CFLAGS hard code the fortification level to 2, use the %_fortify_level macro instead, see "Fortification level" in the build flags guide:

https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/rawhide/f/buildflags.md#source-fortification

This way, fortification will follow the default level chosen for the distribution.
Comment 1 Ben Cotton 2023-02-07 15:05:39 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.