From: "H. Peter Anvin" <hpa@zytor.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Siarhei Liakh <sliakh.lkml@gmail.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-next@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
James Morris <jmorris@namei.org>,
Andrew Morton <akpm@linux-foundation.org>, Andi Kleen <ak@muc.de>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Dave Jones <davej@redhat.com>
Subject: Re: [PATCH V10] RO/NX protection for loadable kernel modules
Date: Mon, 01 Feb 2010 22:06:49 -0800 [thread overview]
Message-ID: <4B67C0F9.2020202@zytor.com> (raw)
In-Reply-To: <201002021429.38331.rusty@rustcorp.com.au>
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?
-hpa
next prev parent reply other threads:[~2010-02-02 6:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 23:39 [PATCH V10] RO/NX protection for loadable kernel modules Siarhei Liakh
2010-02-02 3:59 ` Rusty Russell
2010-02-02 6:06 ` H. Peter Anvin [this message]
2010-02-08 1:29 ` Rusty Russell
2010-10-20 4:45 ` Kees Cook
2010-10-20 5:59 ` Rusty Russell
2010-02-17 19:51 ` [tip:x86/mm] x86: " tip-bot for Siarhei Liakh
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=4B67C0F9.2020202@zytor.com \
--to=hpa@zytor.com \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=sliakh.lkml@gmail.com \
--cc=tglx@linutronix.de \
/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