From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Kees Cook <keescook@chromium.org>
Cc: Chris Metcalf <cmetcalf@mellanox.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tile: handle __ro_after_init like parisc does
Date: Tue, 15 Nov 2016 08:41:52 +0100 [thread overview]
Message-ID: <20161115074152.GA3929@osiris> (raw)
In-Reply-To: <CAGXu5jLHwbGO3gu-_tpikt=WavRVv+5AAv_PDfFf_pKSbb1EKA@mail.gmail.com>
On Mon, Nov 14, 2016 at 01:12:05PM -0800, Kees Cook wrote:
> At some point here, I want to collect all the arch maintainers and
> discuss the options for correctly reflecting the three data
> memory-protection needs we have:
>
> - always read-only
> - read-only after init
> - read-only except during rare updates
>
> (The latter one doesn't exist all yet...)
>
> x86, arm, and arm64 use mark_rodata_ro() after init finishes, so they
> don't technically implement "always read-only". parisc, tile, powerpc,
> others have "always read-only", but disable read-only-after-init since
> they don't use mark_rodata_ro(). I think s390 has recently implemented
> both, but I have to double-check...
Yes, s390 has both: an early always read-only support, which is effective
as soon as paging_init() has set up and enabled page tables.
Our mark_rodata_ro() implementation only makes the ro_after_init section
read-only.
prev parent reply other threads:[~2016-11-15 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 19:50 [PATCH] tile: handle RO_AFTER_INIT_DATA Chris Metcalf
2016-11-08 7:15 ` Heiko Carstens
2016-11-14 20:29 ` [PATCH v2] tile: handle __ro_after_init like parisc does Chris Metcalf
2016-11-14 21:12 ` Kees Cook
2016-11-15 7:41 ` Heiko Carstens [this message]
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=20161115074152.GA3929@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=cmetcalf@mellanox.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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).