This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH 2/2][BZ #12416] Use stack boundaries from /proc/PID/mapsto make stack executable
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Fri, 4 May 2012 16:10:20 -0700 (PDT)
- Subject: Re: [PATCH 2/2][BZ #12416] Use stack boundaries from /proc/PID/mapsto make stack executable
- References: <20120419120021.4780e8c8@spoyarek><20120425203424.A744A2C0CA@topped-with-meat.com><20120426123653.765f1462@spoyarek>
> One reason is that execstack programs set up by the kernel look
> different. This is probably just a cosmetic inconsistency, but it is an
> inconsistency nevertheless. If that is acceptable then we could just
> make pthread_getattr_np return __libc_stack_end rounded up to page
> size as the end of stack rather than the real vma end.
I think that's fine. A program that started with its stack executable is
in fact different from one that loaded a DSO requiring executable stack.