From: Kees Cook <kees.cook@canonical.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
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: RO/NX protection for loadable kernel modules
Date: Sat, 6 Nov 2010 11:28:52 -0700 [thread overview]
Message-ID: <20101106182852.GC5327@outflux.net> (raw)
Peter, anyone? What is the state of this? I can see it in the tip tree,
but it doesn't appear associated with a branch. What will it take to
get this into Linus's tree?
http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commitdiff;h=65187d24fa3ef60f691f847c792e8eaca7e19251
This feature is needed before the function-pointer const-ification patches
will really have any meaning.
Thanks,
-Kees
On Tue, Oct 19, 2010 at 09:45:39PM -0700, Kees Cook wrote:
> On Mon, Feb 08, 2010 at 11:59:44AM +1030, Rusty Russell wrote:
> > 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@rustcorp.com.au>
>
> Sorry for losing track, but where did this patch end up? I don't see it
> in any of the trees I've looked in.
--
Kees Cook
Ubuntu Security Team
reply other threads:[~2010-11-06 18:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101106182852.GC5327@outflux.net \
--to=kees.cook@canonical.com \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=hpa@zytor.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