From: Zev Weiss <zev@bewilderbeest.net>
To: Helge Deller <deller@gmx.de>
Cc: David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
openbmc@lists.ozlabs.org,
"Russell King \(Oracle\)" <linux@armlinux.org.uk>,
Miguel Ojeda <ojeda@kernel.org>,
Florent Revest <revest@chromium.org>,
Kees Cook <keescook@chromium.org>,
Stefan Roesch <shr@devkernel.io>, Sam James <sam@gentoo.org>,
Josh Triplett <josh@joshtriplett.org>,
"Borislav Petkov \(AMD\)" <bp@alien8.de>,
Oleg Nesterov <oleg@redhat.com>,
linux-arm-kernel@lists.infradead.org,
linux-parisc@vger.kernel.org, Yin Fengwei <fengwei.yin@intel.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
stable@vger.kernel.org, Yang Shi <yang@os.amperecomputing.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
"Mike Rapoport \(IBM\)" <rppt@kernel.org>
Subject: Re: [PATCH RESEND 1/2] prctl: Generalize PR_SET_MDWE support check to be per-arch
Date: Tue, 19 Mar 2024 10:37:45 -0700 [thread overview]
Message-ID: <c7bb388b-2c4c-4102-9b84-278f6c6855ee@hatter.bewilderbeest.net> (raw)
In-Reply-To: <e391cad0-7b98-4efd-bea1-cf5ab9c626bf@gmx.de>
On Tue, Feb 27, 2024 at 11:53:59AM PST, Helge Deller wrote:
>On 2/27/24 11:24, Russell King (Oracle) wrote:
>>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.
>
>I'm fine with patch 1/2:
>Acked-by: Helge Deller <deller@gmx.de> # parisc
>
>>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.
>
>I have no preference, but I think both patches should be pushed
>together via arm tree or akpm.
>
>Helge
Ping...Russell, Andrew, any thoughts on how this could move forward?
Thanks,
Zev
next prev parent reply other threads:[~2024-03-19 17:38 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)
2024-02-27 19:53 ` Helge Deller
2024-03-19 17:37 ` Zev Weiss [this message]
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=c7bb388b-2c4c-4102-9b84-278f6c6855ee@hatter.bewilderbeest.net \
--to=zev@bewilderbeest.net \
--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=linux@armlinux.org.uk \
--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 \
/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).