[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201002081159.45219.rusty@rustcorp.com.au>
Date: Mon, 8 Feb 2010 11:59:44 +1030
From: Rusty Russell <rusty@...tcorp.com.au>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Siarhei Liakh <sliakh.lkml@...il.com>,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-next@...r.kernel.org,
Arjan van de Ven <arjan@...radead.org>,
James Morris <jmorris@...ei.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <ak@....de>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Dave Jones <davej@...hat.com>
Subject: Re: [PATCH V10] RO/NX protection for loadable kernel modules
On Tue, 2 Feb 2010 04:36:49 pm H. Peter Anvin wrote:
> On 02/01/2010 07:59 PM, Rusty Russell wrote:
> > On Tue, 2 Feb 2010 10:09:53 am Siarhei Liakh wrote:
> >> This patch is a logical extension of the protection provided by
> >> CONFIG_DEBUG_RODATA to LKMs. The protection is provided by splitting
> >> module_core and module_init into three logical parts each and setting
> >> appropriate page access permissions for each individual section:
> >>
> >> 1. Code: RO+X
> >> 2. RO data: RO+NX
> >> 3. RW data: RW+NX
> >
> > Thanks, applied!
>
> I also applied this to the -tip tree... do you prefer to carry it or
> should I leave it as is?
I'm always happy for you to do my work for me! There are no other module
patches likely to conflict.
Acked-by: Rusty Russell <rusty@...tcorp.com.au>
Cheers,
Rusty.
--
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