From: Kees Cook <keescook@chromium.org>
To: kernel-hardening@lists.openwall.com
Cc: Kees Cook <keescook@chromium.org>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, x86@kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mathias Krause <minipli@googlemail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] expand use of __ro_after_init
Date: Fri, 3 Jun 2016 11:40:22 -0700 [thread overview]
Message-ID: <1464979224-2085-1-git-send-email-keescook@chromium.org> (raw)
After v4.6 released, a number of people complained that Linux's use of
__ro_after_init was extremely limited, but they did not send patches. In
the interest of showing how to make progress in this area, this is a
set of two patches for x86 and arm, extracted from the grsecurity/PaX
patchset in about an hour. I invite others to continue this work, as it
is relatively easy to accomplish.
Since __ro_after_init doesn't yet support modules (assistence here is
welcome too), markings can only be used on variables that are built
in. And since PaX mixes variables that are read-only after init with
those that are protected with pax_open_kernel() and pax_close_kernel(),
it does take a bit of analysis to make sure the variables aren't used
in those cases.
Thanks,
-Kees
next reply other threads:[~2016-06-03 18:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 18:40 Kees Cook [this message]
2016-06-03 18:40 ` [PATCH 0/2] expand use of __ro_after_init Kees Cook
2016-06-03 18:40 ` [PATCH 1/2] x86: apply more __ro_after_init and const Kees Cook
2016-06-03 18:40 ` Kees Cook
2016-06-03 18:40 ` [PATCH 2/2] arm: apply more __ro_after_init Kees Cook
2016-06-03 18:40 ` Kees Cook
2016-06-03 18:51 ` [kernel-hardening] " Greg KH
2016-06-03 21:26 ` Kees Cook
2016-06-03 21:26 ` [kernel-hardening] " Kees Cook
2016-06-03 21:54 ` Greg KH
2016-06-03 21:54 ` Greg KH
2016-06-03 22:01 ` Kees Cook
2016-06-03 22:01 ` Kees Cook
2016-08-10 9:43 ` Russell King - ARM Linux
2016-08-10 9:43 ` Russell King - ARM Linux
2016-08-10 10:00 ` Arnd Bergmann
2016-08-10 10:00 ` Arnd Bergmann
2016-08-10 10:12 ` Russell King - ARM Linux
2016-08-10 10:12 ` Russell King - ARM Linux
2016-08-10 19:31 ` Arnd Bergmann
2016-08-10 19:31 ` Arnd Bergmann
2016-08-10 23:02 ` Russell King - ARM Linux
2016-08-11 16:02 ` Arnd Bergmann
2016-08-11 16:02 ` Arnd Bergmann
2016-08-12 11:34 ` Daniel Thompson
2016-08-12 11:34 ` Daniel Thompson
2016-08-10 17:06 ` Daniel Micay
2016-08-10 17:06 ` [kernel-hardening] " Daniel Micay
2016-08-10 18:32 ` Kees Cook
2016-08-10 18:32 ` Kees Cook
2016-08-10 19:41 ` Arnd Bergmann
2016-08-10 19:41 ` Arnd Bergmann
2016-08-10 21:40 ` Kees Cook
2016-08-10 23:06 ` Russell King - ARM Linux
2016-08-11 15:54 ` Arnd Bergmann
2016-08-11 15:54 ` Arnd Bergmann
2016-08-11 22:16 ` Kees Cook
2016-08-12 16:24 ` Russell King - ARM Linux
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=1464979224-2085-1-git-send-email-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=x86@kernel.org \
/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).