[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <56C5A112.25195.35DDEA@pageexec.freemail.hu>
Date: Thu, 18 Feb 2016 11:46:42 +0100
From: "PaX Team" <pageexec@...email.hu>
To: David Brown <david.brown@...aro.org>, Kees Cook <keescook@...omium.org>
CC: Russell King <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Ingo Molnar <mingo@...hat.com>, Andy Lutomirski <luto@...capital.net>,
"H. Peter Anvin" <hpa@...or.com>,
Michael Ellerman <mpe@...erman.id.au>,
Mathias Krause <minipli@...glemail.com>,
Thomas Gleixner <tglx@...utronix.de>,
"x86@...nel.org" <x86@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Emese Revfy <re.emese@...il.com>, LKML <linux-kernel@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH] ARM: vdso: Mark vDSO code as read-only
On 17 Feb 2016 at 15:48, Kees Cook wrote:
> On Wed, Feb 17, 2016 at 3:43 PM, David Brown <david.brown@...aro.org> wrote:
> > Is there a possible future consideration to perhaps make .rodata read
> > only much earlier?
>
> Yeah, this will likely be a future improvement. Some architectures
> already mark .rodata before the mark_rodata_ro() call. Once we start
> to have more use of postinit-readonly, I suspect we'll see more
> clarification of when those things happen.
FYI, PaX had enforced early rodata on i386 during the 2.4 series (i.e.,
decade+ ago) but i abandoned it for 2.6 due to the maintenance burden
coupled with its low benefit...
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
