[PATCH 2/2][BZ #12416] Use stack boundaries from /proc/PID/maps to make stack executable

[Roland McGrath]

> 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.


Thanks,
Roland