Bug 147296 - ppc64 libgcc.a has RWE PT_GNU_STACK marking
ppc64 libgcc.a has RWE PT_GNU_STACK marking
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: binutils (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Brian Stein
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-02-06 12:46 EST by Brian Stein
Modified: 2013-03-01 00:14 EST (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2005-259
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-09 06:59:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Arjan van de Ven 2005-02-06 12:46:34 EST
Description of problem:
RHEL4 libgcc.a on ppc64 has a RWE PT_GNU_STACK marking, this results
in the entire distro to run with executable stack markings on ppc64.
Comment 1 Jakub Jelinek 2005-02-09 10:04:45 EST
This sounds like binutils bug.  On ppc64:
echo '.section .note.GNU-stack,"",@progbits' | as -o a.o -
echo '.section .note.GNU-stack,"",@progbits' | as -o b.o -
ld -r -o c.o [ab].o
readelf -WS [abc].o | grep .note.GNU-stack
  [ 4] .note.GNU-stack   PROGBITS        0000000000000000 000040 000000 00      0
  0  1
  [ 4] .note.GNU-stack   PROGBITS        0000000000000000 000040 000000 00      0
  0  1
  [ 4] .note.GNU-stack   PROGBITS        0000000000000000 000040 000000 00   X  0
  0  1

while on e.g. x86_64 all 3 of them are non-X.
Comment 3 Jakub Jelinek 2005-02-13 11:38:57 EST
Fixed for FC4 in binutils-2.15.94.0.2-1.
Comment 5 Tim Powers 2005-06-09 06:59:49 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-259.html

Note You need to log in before you can comment on or make changes to this bug.