From: Valdis.Kletnieks@vt•edu
To: Steven Rostedt <rostedt@goodmis•org>
Cc: Ingo Molnar <mingo@elte•hu>, mat <castet.matthieu@free•fr>,
Kees Cook <kees.cook@canonical•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>,
"H. Peter Anvin" <hpa@zytor•com>,
Rusty Russell <rusty@rustcorp•com.au>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Dave Jones <davej@redhat•com>,
Siarhei Liakh <sliakh.lkml@gmail•com>
Subject: Re: [PATCH 3/3 V13] RO/NX protection for loadable kernel
Date: Thu, 23 Dec 2010 20:43:50 -0500 [thread overview]
Message-ID: <63168.1293155030@localhost> (raw)
In-Reply-To: Your message of "Thu, 23 Dec 2010 10:01:48 EST." <1293116508.22802.14.camel@gandalf.stny.rr.com>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Thu, 23 Dec 2010 10:01:48 EST, Steven Rostedt said:
> On Wed, 2010-12-22 at 16:35 -0500, Valdis.Kletnieks@vt•edu wrote:
>
> > Steve Rostedt's patch that moves the setting of the page permissions seems to
> > make this patch no longer necessary. I tripped over this same issue, but the
> > version in the latest -mmotm does not need it, as it includes Steve's fix.
>
> Can I add your "Tested-by: ..." to the commit?
Sure. I can verify that the patch series (a) doesn't break well-behaved
modules and (b) it *does* trigger for misbehaving modules (I sent the
VirtualBox crew a bug report for a module that tried to write to an area
marked executable).
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-12-24 1:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 21:35 [PATCH 3/3 V13] RO/NX protection for loadable kernel matthieu castet
2010-11-25 3:41 ` Valdis.Kletnieks
2010-11-26 17:23 ` mat
2010-11-29 16:59 ` Valdis.Kletnieks
2010-12-08 22:19 ` Kees Cook
2010-12-10 23:18 ` mat
2010-12-11 0:27 ` Kees Cook
[not found] ` <20101211115735.21b616fe@mat-laptop>
2010-12-11 23:15 ` Kees Cook
2010-12-22 12:40 ` Ingo Molnar
2010-12-22 21:35 ` Valdis.Kletnieks
2010-12-22 21:57 ` Ingo Molnar
2010-12-22 22:02 ` Steven Rostedt
2010-12-23 8:49 ` Ingo Molnar
2010-12-23 15:01 ` Steven Rostedt
2010-12-24 1:43 ` Valdis.Kletnieks [this message]
2011-01-07 9:34 ` Xiaotian Feng
2011-01-07 13:04 ` Ingo Molnar
2011-01-08 11:24 ` matthieu castet
2011-01-10 23:49 ` Kees Cook
2011-01-11 22:42 ` matthieu castet
2011-01-20 20:32 ` matthieu castet
2011-01-21 2:35 ` Xiaotian Feng
2010-11-29 18:15 ` Steven Rostedt
2010-11-29 23:35 ` Rusty Russell
2010-11-30 14:46 ` Steven Rostedt
2010-12-01 13:36 ` Rusty Russell
2010-11-30 21:20 ` mat
2010-12-01 0:38 ` Steven Rostedt
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=63168.1293155030@localhost \
--to=valdis.kletnieks@vt$(echo .)edu \
--cc=ak@muc$(echo .)de \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arjan@infradead$(echo .)org \
--cc=castet.matthieu@free$(echo .)fr \
--cc=davej@redhat$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=jmorris@namei$(echo .)org \
--cc=kees.cook@canonical$(echo .)com \
--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=rostedt@goodmis$(echo .)org \
--cc=rusty@rustcorp$(echo .)com.au \
--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