This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Enable no-exec stacks for more targets using the Linux kernel
- From: Michael Eager <eager at eagerm dot com>
- To: Andreas Schwab <schwab at suse dot de>, Joseph Myers <joseph at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, law at redhat dot com, dave dot anglin at bell dot net, wilson at tuliptree dot org, eager at eagercon dot com
- Date: Tue, 19 Sep 2017 08:34:47 -0700
- Subject: Re: Enable no-exec stacks for more targets using the Linux kernel
- Authentication-results: sourceware.org; auth=none
- References: <alpine.DEB.2.20.1709182201230.12317@digraph.polyomino.org.uk> <mvmo9q76tss.fsf@suse.de>
On 09/19/2017 12:17 AM, Andreas Schwab wrote:
On Sep 18 2017, Joseph Myers <joseph@codesourcery.com> wrote:
Building glibc for many different configurations and running the
compilation parts of the testsuite runs into failures of the
elf/check-execstack test for hppa, ia64 and microblaze.
ia64 is non-execstack by default, so it doesn't need any marking. The
same is true for every architecture that doesn't override
elf_read_implies_exec, which includes microblaze and hppa.
This fails because those configurations are not generating
.note.GNU-stack sections to indicate that programs do not need an
executable stack.
This needs to be fixed in glibc.
The requirement that a null .note.GNU-stack section needs to be defined
to indicate that the default stack (i.e., non-executable) is used seems
backward.
I don't have any problem approving the MicroBlaze GCC changes, but, like
Andreas, I think that this is a glibc problem.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077