public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp•com.au>
To: Siarhei Liakh <sliakh.lkml@gmail•com>
Cc: 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>,
	"H. Peter Anvin" <hpa@zytor•com>, 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: Tue, 2 Feb 2010 14:29:38 +1030	[thread overview]
Message-ID: <201002021429.38331.rusty@rustcorp.com.au> (raw)
In-Reply-To: <817ecb6f1002011539g3f30416fi60c7c5222cab8f3@mail.gmail.com>

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!

Cheers,
Rusty.

  reply	other threads:[~2010-02-02  3:59 UTC|newest]

Thread overview: 6+ 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 [this message]
2010-02-02  6:06   ` H. Peter Anvin
2010-02-08  1:29     ` Rusty Russell
2010-10-20  4:45       ` Kees Cook
2010-10-20  5:59         ` Rusty Russell

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=201002021429.38331.rusty@rustcorp.com.au \
    --to=rusty@rustcorp$(echo .)com.au \
    --cc=ak@muc$(echo .)de \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=arjan@infradead$(echo .)org \
    --cc=davej@redhat$(echo .)com \
    --cc=hpa@zytor$(echo .)com \
    --cc=jmorris@namei$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-security-module@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=sliakh.lkml@gmail$(echo .)com \
    --cc=tglx@linutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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