From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave.anglin@bell.net>, Sam James <sam@gentoo.org>
Cc: "linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>
Subject: Re: prctl call wrongly succeeds on HPPA?
Date: Fri, 10 Nov 2023 21:38:49 +0100 [thread overview]
Message-ID: <cf75a1e4-c269-4530-b3aa-b02a81597acb@gmx.de> (raw)
In-Reply-To: <7409ec05-7a28-45fe-9604-519de5ae934e@bell.net>
On 11/10/23 21:12, John David Anglin wrote:
> On 2023-11-10 3:01 p.m., Helge Deller wrote:
>>>> On HPPA, we still need executable stacks, so this option doesn't work
>>>> and leads to a segfault on boot.
>>
>> For kernel we don't need it any longer.
>> But there might be dependencies on glibc version and/or combination.
>> So, I've currently lost overview if we still need executable stacks...
> FWIW, I recently changed gcc-14 to enable GNU stack notes and fixed a bug in the
> 32-bit PA 2.0 trampoline template. All execute stack tests in glibc now pass with gcc-14.
Yes, I saw your commits.
So, any code compiled with >= gcc-14 should be fine with non-writeable stacks?
It would be easier if it would be a glibc dependency (for distribution maintainers)...
> gdb still needs a fix in unwind code.
Ok.
Helge
next prev parent reply other threads:[~2023-11-10 20:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 4:32 prctl call wrongly succeeds on HPPA? Sam James
2023-11-03 12:53 ` Sam James
2023-11-10 20:01 ` Helge Deller
2023-11-10 20:12 ` John David Anglin
2023-11-10 20:38 ` Helge Deller [this message]
2023-11-10 21:08 ` John David Anglin
2023-11-10 21:32 ` Sam James
2023-11-10 22:00 ` John David Anglin
2023-11-10 22:16 ` Sam James
2023-11-10 23:02 ` John David Anglin
2023-11-17 14:55 ` Helge Deller
2023-11-17 15:41 ` John David Anglin
2023-11-18 5:52 ` Sam James
2023-11-19 12:11 ` Sam James
2023-11-10 20:12 ` Sam James
2023-11-10 20:25 ` Helge Deller
2023-11-10 20:31 ` Helge Deller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf75a1e4-c269-4530-b3aa-b02a81597acb@gmx.de \
--to=deller@gmx.de \
--cc=dave.anglin@bell.net \
--cc=linux-parisc@vger.kernel.org \
--cc=sam@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.