From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Jann Horn <jannh@google.com>
Cc: Kees Cook <keescook@chromium.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Emese Revfy <re.emese@gmail.com>,
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default
Date: Fri, 14 Jun 2019 17:28:11 +0100 [thread overview]
Message-ID: <20190614162811.o33yeq65ythjumrh@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAG48ez30+VOj78rCiWMKtm0tHdVR67CcrHVCV-FFCfK-nRQTOw@mail.gmail.com>
On Fri, Jun 14, 2019 at 06:05:19PM +0200, Jann Horn wrote:
> +32-bit ARM folks
>
> On Fri, Jun 14, 2019 at 5:10 PM Denis 'GNUtoo' Carikli
> <GNUtoo@cyberdimension.org> wrote:
> > On a Galaxy SIII (I9300), the patch mentioned below broke boot:
> > - The display still had the bootloader logo, while with this
> > patch, the 4 Tux logo appears.
> > - No print appeared on the serial port anymore after the kernel
> > was loaded, whereas with this patch, we have the serial
> > console working, and the device booting.
> >
> > Booting was broken by the following commit:
> > 9f671e58159a ("security: Create "kernel hardening" config area")
> >
> > As the bootloader of this device enables the MMU, I had the following
> > patch applied during the tests:
> > Author: Arve Hjønnevåg <arve@android.com>
> > Date: Fri Nov 30 17:05:40 2012 -0800
> >
> > ANDROID: arm: decompressor: Flush tlb before swiching domain 0 to client mode
> >
> > If the bootloader used a page table that is incompatible with domain 0
> > in client mode, and boots with the mmu on, then swithing domain 0 to
> > client mode causes a fault if we don't flush the tlb after updating
> > the page table pointer.
> >
> > v2: Add ISB before loading dacr.
I'm wondering whether this is sloppy wording or whether the author is
really implying that they call the kernel decompressor with the MMU
enabled, against the express instructions in Documentation/arm/Booting.
If they are going against the express instructions, all bets are off.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-14 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190614145755.10926-1-GNUtoo@cyberdimension.org>
2019-06-14 16:05 ` [PATCH] security: do not enable CONFIG_GCC_PLUGINS by default Jann Horn
2019-06-14 16:12 ` Denis 'GNUtoo' Carikli
2019-06-14 16:28 ` Russell King - ARM Linux admin [this message]
2019-06-14 18:14 ` Denis 'GNUtoo' Carikli
2019-06-14 18:54 ` Russell King - ARM Linux admin
2019-06-15 10:13 ` Paul Kocialkowski
2019-06-21 23:42 ` Denis 'GNUtoo' Carikli
2019-06-24 13:31 ` Paul Kocialkowski
2019-06-15 3:08 ` Kees Cook
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=20190614162811.o33yeq65ythjumrh@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=GNUtoo@cyberdimension.org \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=re.emese@gmail.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).