From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: linux-parisc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Helge Deller <deller@gmx.de>,
Florent Revest <revest@chromium.org>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Yin Fengwei <fengwei.yin@intel.com>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Yang Shi <yang@os.amperecomputing.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Oleg Nesterov <oleg@redhat.com>,
David Hildenbrand <david@redhat.com>,
Stefan Roesch <shr@devkernel.io>,
Josh Triplett <josh@joshtriplett.org>,
Ondrej Mosnacek <omosnace@redhat.com>,
Miguel Ojeda <ojeda@kernel.org>,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
Sam James <sam@gentoo.org>,
stable@vger.kernel.org
Subject: Re: [PATCH RESEND 1/2] prctl: Generalize PR_SET_MDWE support check to be per-arch
Date: Tue, 27 Feb 2024 10:24:40 +0000 [thread overview]
Message-ID: <Zd24aCps4xD28c74@shell.armlinux.org.uk> (raw)
In-Reply-To: <20240227013546.15769-5-zev@bewilderbeest.net>
On Mon, Feb 26, 2024 at 05:35:41PM -0800, Zev Weiss wrote:
> There exist systems other than PARISC where MDWE may not be feasible
> to support; rather than cluttering up the generic code with additional
> arch-specific logic let's add a generic function for checking MDWE
> support and allow each arch to override it as needed.
>
> Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
> Cc: <stable@vger.kernel.org> # v6.3+
PA-RISC folk need to ack/review-by this patch. Alternatively, it needs
to be restructured to add the arch_memory_deny_write_exec_supported()
override without touching the PA-RISC code, which then makes the Arm
patch independent of the status of the PA-RISC patch. That will allow
the Arm issue to be solved even if an ack is not forthcoming for the
PA-RISC parts.
Alternatively, I wonder whether akpm would be willing to pick up this
patch set as-is.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-27 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 1:35 [PATCH RESEND 0/2] ARM: prctl: Reject PR_SET_MDWE where not supported Zev Weiss
2024-02-27 1:35 ` [PATCH RESEND 1/2] prctl: Generalize PR_SET_MDWE support check to be per-arch Zev Weiss
2024-02-27 10:24 ` Russell King (Oracle) [this message]
2024-02-27 19:53 ` Helge Deller
2024-03-19 17:37 ` Zev Weiss
2024-02-27 1:35 ` [PATCH RESEND 2/2] ARM: prctl: Reject PR_SET_MDWE on pre-ARMv6 Zev Weiss
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=Zd24aCps4xD28c74@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=david@redhat.com \
--cc=deller@gmx.de \
--cc=fengwei.yin@intel.com \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=oleg@redhat.com \
--cc=omosnace@redhat.com \
--cc=openbmc@lists.ozlabs.org \
--cc=revest@chromium.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=sam@gentoo.org \
--cc=shr@devkernel.io \
--cc=stable@vger.kernel.org \
--cc=yang@os.amperecomputing.com \
--cc=zev@bewilderbeest.net \
/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 NNTP newsgroup(s).