All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: 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:01:50 +0100	[thread overview]
Message-ID: <0fec2446-a523-486f-9df7-4c6af9e2e0e3@gmx.de> (raw)
In-Reply-To: <875y2jro9a.fsf@gentoo.org>

On 11/3/23 13:53, Sam James wrote:
> Sam James <sam@gentoo.org> writes:
>> I recently hit an issue with systemd-254 which tries to use the new
>> prctl(PR_SET_MDWE) for systemd's MemoryDenyWriteExecute functionality.

Is this still a problem?

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

>> Should this call be succeeeding on HPPA, or should we reject it for
>> now until we have things wired up?
>>
>> Reported to systemd at https://github.com/systemd/systemd/issues/29775.
>
> Lennart has made clear (and I don't think I disagree) that he considers
> this squarely a kernel bug.

I've read the various bug reports and looked at the kernel commits regarding, e.g.

commit b507808ebce23561d4ff8c2aa1fb949fe402bc61
Author: Joey Gouly <joey.gouly@arm.com>
Date:   Thu Jan 19 16:03:43 2023 +0000

     mm: implement memory-deny-write-execute as a prctl

but what is prctl(PR_SET_MDWE, PR_MDWE*, 0, 0)... expected to return on parisc?
EINVAL? ENOTSUP?

Helge

  reply	other threads:[~2023-11-10 20:02 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 [this message]
2023-11-10 20:12     ` John David Anglin
2023-11-10 20:38       ` Helge Deller
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=0fec2446-a523-486f-9df7-4c6af9e2e0e3@gmx.de \
    --to=deller@gmx.de \
    --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.