Bug 1105456

Summary: delete --param ssp-buffer-size=4 in the build
Product: [Community] Virtualization Tools Reporter: Agostino Sarubbo <ago>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, jtomko
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-12 06:38:07 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:

Description Agostino Sarubbo 2014-06-06 07:46:17 UTC 
Description of problem:
I noticed that on my build of libvirt, I have -fstack-protector-all --param ssp-buffer-size=4.
This make no sense because -fstack-protector-all is covering all, so you don't need to specify the minimum buffer size to cover.

--param ssp-buffer-size is used with -fstack-protector which theoretically covers the buffers of >=8


Version-Release number of selected component (if applicable):
1.2.3


How reproducible:
Just compile and check the output



Expected results:
Have only -fstack-protector-all
Comment 1 Ján Tomko 2014-06-12 06:38:07 UTC 
Fixed upstream by
commit 5567baa973ae855fe849e0ef32fb6b7f3eaa0bf0
Author:     Ján Tomko <jtomko>
CommitDate: 2014-06-12 08:16:03 +0200

    build: remove ssp-buffer-size
git describe: v1.2.5-104-g5567baa