From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 57B97C4332F for ; Tue, 31 Oct 2023 04:34:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230100AbjJaEeM (ORCPT ); Tue, 31 Oct 2023 00:34:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55022 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229504AbjJaEeM (ORCPT ); Tue, 31 Oct 2023 00:34:12 -0400 Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1269EA9 for ; Mon, 30 Oct 2023 21:34:10 -0700 (PDT) User-agent: mu4e 1.10.7; emacs 30.0.50 From: Sam James To: "linux-parisc@vger.kernel.org" Subject: prctl call wrongly succeeds on HPPA? Date: Tue, 31 Oct 2023 04:32:36 +0000 Organization: Gentoo Message-ID: <87lebjz9z6.fsf@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org I recently hit an issue with systemd-254 which tries to use the new prctl(PR_SET_MDWE) for systemd's MemoryDenyWriteExecute functionality. On HPPA, we still need executable stacks, so this option doesn't work and leads to a segfault on boot. 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. thanks, sam