public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Siarhei Liakh <sliakh.lkml@gmail•com>
To: Rusty Russell <rusty@rustcorp•com.au>
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>
Subject: Re: [PATCH v6] RO/NX protection for loadable kernel modules
Date: Tue, 22 Sep 2009 11:50:21 -0400	[thread overview]
Message-ID: <817ecb6f0909220850m4127b382h12fafd1e6182a292@mail.gmail.com> (raw)
In-Reply-To: <200909220929.32301.rusty@rustcorp.com.au>

> This is usually considered a bad idea.  Make a new config option,
> CONFIG_HAVE_SET_MEMORY_PROTECTION, select it in arch/x86/Kconfig.
> Then wrap the entire functions in one #ifdef CONFIG_HAVE_....
> and put empty versions in the #else.

Ok, will do.
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo@vger•kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-09-22 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11  2:50 [PATCH v6] RO/NX protection for loadable kernel modules Siarhei Liakh
2009-09-21 21:40 ` Dave Jones
2009-09-22 15:49   ` Siarhei Liakh
2009-10-05 11:57     ` Siarhei Liakh
2009-09-21 23:59 ` Rusty Russell
2009-09-22 15:50   ` Siarhei Liakh [this message]

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=817ecb6f0909220850m4127b382h12fafd1e6182a292@mail.gmail.com \
    --to=sliakh.lkml@gmail$(echo .)com \
    --cc=ak@muc$(echo .)de \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=arjan@infradead$(echo .)org \
    --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=rusty@rustcorp$(echo .)com.au \
    --cc=sfr@canb$(echo .)auug.org.au \
    --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