From: Matthew Wilcox <willy@infradead.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Tony Luck <tony.luck@intel.com>,
arnd@arndb.de, gregkh@linuxfoundation.org,
linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] mm: provide a fallback for PAGE_KERNEL_RO for architectures
Date: Tue, 8 May 2018 18:39:35 -0700 [thread overview]
Message-ID: <20180509013935.GA8131@bombadil.infradead.org> (raw)
In-Reply-To: <20180509010438.GM27853@wotan.suse.de>
On Wed, May 09, 2018 at 01:04:38AM +0000, Luis R. Rodriguez wrote:
> On Fri, Apr 27, 2018 at 08:18:10PM -0700, Matthew Wilcox wrote:
> > ia64: Add PAGE_KERNEL_RO and PAGE_KERNEL_EXEC
> >
> > The rest of the kernel was falling back to simple PAGE_KERNEL pages; using
> > PAGE_KERNEL_RO and PAGE_KERNEL_EXEC provide better protection against
> > unintended writes.
> >
> > Signed-off-by: Matthew Wilcox <mawilcox@microsoft.com>
>
> Nice, should I queue this into my series as well?
A little reluctant to queue it without anyone having tested it. Heck,
I didn't even check it compiled ;-)
We used to just break architectures and let them fix it up for this kind
of thing. That's not really acceptable nowadays, but I don't know how
we get arch maintainers to fix up their ports now.
next prev parent reply other threads:[~2018-05-09 1:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 0:15 [PATCH] mm: provide a fallback for PAGE_KERNEL_RO for architectures Luis R. Rodriguez
2018-04-28 3:18 ` Matthew Wilcox
2018-05-09 1:04 ` Luis R. Rodriguez
2018-05-09 1:39 ` Matthew Wilcox [this message]
2018-05-10 1:15 ` Luis R. Rodriguez
2018-04-28 5:04 ` Greg KH
2018-05-02 10:08 ` Geert Uytterhoeven
2018-05-02 15:11 ` Luis R. Rodriguez
2018-05-10 1:24 ` Luis R. Rodriguez
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=20180509013935.GA8131@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=arnd@arndb.de \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=tony.luck@intel.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 NNTP newsgroup(s).