[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140214162257.GB2331@e103592.cambridge.arm.com>
Date: Fri, 14 Feb 2014 16:22:57 +0000
From: Dave Martin <Dave.Martin@....com>
To: Kees Cook <keescook@...omium.org>
Cc: linux-arm-kernel@...ts.infradead.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Larry Bassel <lbassel@...eaurora.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Russell King <linux@....linux.org.uk>,
Nicolas Pitre <nico@...aro.org>,
Ben Dooks <ben.dooks@...ethink.co.uk>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Grant Likely <grant.likely@...aro.org>,
Jiang Liu <liuj97@...il.com>,
Christoffer Dall <cdall@...columbia.edu>,
Laura Abbott <lauraa@...eaurora.org>,
Marc Zyngier <marc.zyngier@....com>,
Rob Herring <rob.herring@...xeda.com>,
Vitaly Andrianov <vitalya@...com>,
Jonathan Austin <jonathan.austin@....com>,
Simon Baatz <gmbnomis@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org,
Santosh Shilimkar <santosh.shilimkar@...com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 2/2] ARM: mm: keep rodata non-executable
On Thu, Feb 13, 2014 at 05:04:10PM -0800, Kees Cook wrote:
> Introduce "CONFIG_DEBUG_RODATA" to mostly match the x86 config, though
> the behavior is different: it depends on STRICT_KERNMEM_PERMS, which
> sets rodata read-only (but executable), where as this option additionally
> splits rodata from the kernel text (resulting in potentially more memory
> lost to padding) and sets it non-executable as well. The end result is
> that on builds with CONFIG_DEBUG_RODATA=y (like x86) the rodata with be
> marked purely read-only.
This triggers an Oops in kexec, because we have a block of code in .text
which is a template for generating baremetal code to relocate the new
kernel, and some literal words are written into it before copying.
Possibly this should be in .rodata, not .text.
There may be a few other instances of this kind of thing.
Are you aware of similar situations on other arches?
Cheers
---Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists