From: Ingo Molnar <mingo@elte.hu>
To: James Morris <jmorris@namei.org>
Cc: Siarhei Liakh <sliakh.lkml@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>, Andi Kleen <ak@muc.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] RO/NX protection for loadable kernel modules
Date: Tue, 23 Jun 2009 12:00:40 +0200 [thread overview]
Message-ID: <20090623100040.GD30634@elte.hu> (raw)
In-Reply-To: <alpine.LRH.2.00.0906231240060.31540@tundra.namei.org>
* James Morris <jmorris@namei.org> wrote:
> On Thu, 18 Jun 2009, 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
> >
> > In order to achieve proper protection, layout_sections() have been
> > modified to align each of the three parts mentioned above onto page
> > boundary. Next, the corresponding page access permissions are set
> > right before successful exit from load_module(). Further,
> > module_free() have been modified to set module_core or module_init as
> > RW+NX right before calling vfree(). Functionality of this patch is
> > enabled only when CONFIG_DEBUG_RODATA defined at compile time.
> >
>
> This looks potentially useful to me, but I'm not an x86 expert
> (several now added to Cc:).
Pinged a few folks about this already. It looks useful, with the
main worry being:
1) the increase in effective module size (probably worth the price)
2) some uglies in the patch (fixable)
The main ugliness is the excessive use of #ifdefs - those should be
eliminated. Also, most scripts/checkpatch.pl warnings about this
patch should be taken seriously.
Ingo
next prev parent reply other threads:[~2009-06-23 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 1:33 [PATCH] RO/NX protection for loadable kernel modules Siarhei Liakh
2009-06-23 2:43 ` James Morris
2009-06-23 10:00 ` Ingo Molnar [this message]
2009-06-24 15:53 ` 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=20090623100040.GD30634@elte.hu \
--to=mingo@elte.hu \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rusty@rustcorp.com.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.