From: Faraz Shahbazker <fshahbazker@wavecomp.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Dragan Mladjenovic <dmladjenovic@wavecomp.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
Carlos O'Donell <carlos@redhat.com>,
"Maciej W . Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH v2 0/3] Mips support for PT_GNU_STACK
Date: Thu, 18 Jul 2019 15:34:11 +0000 [thread overview]
Message-ID: <MWHPR22MB023982DA44E597C866E0614AD0C80@MWHPR22MB0239.namprd22.prod.outlook.com> (raw)
In-Reply-To: e5641987-f618-0a51-0bd8-ef56efa0b23a@linaro.org
On 7/18/19 6:38 AM, Adhemerval Zanella wrote:> On 17/07/2019 19:59, Faraz Shahbazker wrote:
>> On 07/17/2019 12:43 PM, Adhemerval Zanella wrote:
>> IMO, the current behaviour of PT_GNU_STACK for MIPS is an anomaly in itself. What should
>> have been, is a rejection of non-executable PT_GNU_STACK at some level, instead of silently
>> overriding it in glibc. So are you of the opinion that this change in glibc behaviour is not
>> worth being published at all, or that it should be advertised using a different mechanism
>> instead of an ABI version bump?
>
> Since non-executable stack is tied with underlying kernel support rather than
> ABI, my suggestion is just to assume non-executable stack as default, without
> permission override, if glibc is configure for kernel higher than *4.8*. We will
> need to live with old behaviour for default builds.
Frankly, I can live with that. If someone really wants to back-port they have to do the
leg-work across multiple components to get it to work. This theoretically still leaves
the door open for the kernel to start advertising non-exec stack support to allow for
easier back-ports.
Regards,
Faraz
next prev parent reply other threads:[~2019-07-18 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 18:23 [PATCH v2 0/3] Mips support for PT_GNU_STACK Dragan Mladjenovic
2019-07-16 11:15 ` [PATCH v2 1/3] [ELF] Allow the machine support to enforce executable stack Dragan Mladjenovic
2019-07-16 11:16 ` [PATCH v2 2/3] [MIPS] Define DL_EXEC_STACK_OVERRIDE Dragan Mladjenovic
2019-07-16 11:16 ` [PATCH v2 3/3] [RFC][MIPS] Define GNU_STACK ABI Dragan Mladjenovic
2019-07-17 19:43 ` [PATCH v2 0/3] Mips support for PT_GNU_STACK Adhemerval Zanella
2019-07-17 21:47 ` Dragan Mladjenovic
2019-07-18 13:33 ` Adhemerval Zanella
2019-07-18 20:00 ` Dragan Mladjenovic
2019-07-17 22:59 ` Faraz Shahbazker
2019-07-18 13:38 ` Adhemerval Zanella
2019-07-18 15:34 ` Faraz Shahbazker [this message]
2019-07-18 19:49 ` Dragan Mladjenovic
2019-07-18 20:54 ` Adhemerval Zanella
2019-07-18 14:50 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR22MB023982DA44E597C866E0614AD0C80@MWHPR22MB0239.namprd22.prod.outlook.com \
--to=fshahbazker@wavecomp.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=dmladjenovic@wavecomp.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).