From: Arjan van de Ven <arjan@infradead.org>
To: Siarhei Liakh <sliakh.lkml@gmail.com>
Cc: James Morris <jmorris@namei.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, Andi Kleen <ak@muc.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v2] RO/NX protection for loadable kernel modules
Date: Tue, 30 Jun 2009 21:58:13 -0700 [thread overview]
Message-ID: <20090630215813.52ee354c@infradead.org> (raw)
In-Reply-To: <817ecb6f0906300744i4f11d7faldd10ef3834582812@mail.gmail.com>
On Tue, 30 Jun 2009 10:44:46 -0400
Siarhei Liakh <sliakh.lkml@gmail.com> wrote:
> >>
> >> Given that it will not reduce the number of #ifdefs, do you still
> >> think that NX should be made unconditional?
> >
> > I think that not only NX should be made unconditional, I also think
> > that the RO code should be unconditional.
>
> So, the only conditional part would be the page-alignment of each of
> the three parts of a module. Is that correct understanding?
yep
(and for me, even that is debatable, but I can see the point for having
that conditional)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
prev parent reply other threads:[~2009-07-01 4:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 15:16 Siarhei Liakh
2009-06-29 15:30 ` Arjan van de Ven
2009-06-29 19:54 ` Ingo Molnar
2009-06-30 13:11 ` Siarhei Liakh
2009-06-30 13:29 ` Arjan van de Ven
2009-06-30 14:44 ` Siarhei Liakh
2009-07-01 4:58 ` Arjan van de Ven [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=20090630215813.52ee354c@infradead.org \
--to=arjan@infradead.org \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®