linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
	Kees Cook <keescook@chromium.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"x86@kernel.org" <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mathias Krause <minipli@googlemail.com>
Subject: Re: [PATCH 2/2] arm: apply more __ro_after_init
Date: Thu, 11 Aug 2016 17:54:08 +0200	[thread overview]
Message-ID: <2188666.QKZtt2vNXZ@wuerfel> (raw)
In-Reply-To: <20160810230645.GP1041@n2100.armlinux.org.uk>

On Thursday, August 11, 2016 12:06:45 AM CEST Russell King - ARM Linux wrote:
> On Wed, Aug 10, 2016 at 09:41:23PM +0200, Arnd Bergmann wrote:
> > It might be better to start by making the fixed mapping readonly,
> > as KASLR doesn't protect that one at all, and change the TLS
> > code accordingly.
> 
> I think that's impossible, because we gave userspace permission to
> read 0xffff0ff0 directly without using __kuser_get_tls.  You're
> talking about potentially breaking userspace.
> 
> If you disable kuser helpers, then the page becomes read-only and
> invisible to userspace anyway.  So, everything is being done there
> which can be done - if you have kuser helpers enabled, then you
> lose some opportunities for these security improvements.

What I meant was writing to the page through the linear mapping
rather than the virtual mapping at 0xffff0000 so we can leave that
one read-only (I did not consider whether that might cause cache
aliasing problems when reading from the other address).

Your other point is more important though: if one really cares
about optimizing security here, they probably should disable
kuser helpers completely anyway.

Kees, is that something you have on your radar already?

	Arnd

  reply	other threads:[~2016-08-11 15:54 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 18:40 [PATCH 0/2] expand use of __ro_after_init Kees Cook
2016-06-03 18:40 ` 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 [this message]
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=2188666.QKZtt2vNXZ@wuerfel \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=keescook@chromium.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=linux@armlinux.org.uk \
    --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).