linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Siarhei Liakh <sliakh.lkml@gmail.com>
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>,
	Dave Jones <davej@redhat.com>
Subject: Re: [PATCH V9] RO/NX protection for loadable kernel modules
Date: Tue, 2 Feb 2010 08:19:55 +1030	[thread overview]
Message-ID: <201002020819.55499.rusty@rustcorp.com.au> (raw)
In-Reply-To: <817ecb6f1002010829m712ffff4hfb64ff3ea236e1f1@mail.gmail.com>

On Tue, 2 Feb 2010 02:59:41 am Siarhei Liakh wrote:
> V9: coding style fixes

But not compile tested:

> +void set_page_attributes(void *start, void *end,
> +		void (*set)(unsigned long start, int num_pages))
> +{
> +	unsigned long begin_pfn = PFN_DOWN((unsigned long)start);
> +	unsigned long end_pfn = PFN_DOWN((unsigned long)end);
> +	if (end_pfn > begin_pfn)
> +		set(begin_pfn << PAGE_SHIFT, end_pfn - begin_pfn);
> +}
...
> +	if (ro_size > 0) {
> +		set_page_attributes((unsigned long)base,
> +					(unsigned long)base + ro_size,
> +					set_memory_ro);

The casts here should cause a warning. 

> +	if (total_size > text_size) {
> +		begin_pfn = PFN_UP((unsigned long)base + text_size);
> +		end_pfn = PFN_UP((unsigned long)base + total_size);
> +		if (end_pfn > begin_pfn)
> +			set_memory_nx(begin_pfn << PAGE_SHIFT,
> +						end_pfn - begin_pfn);

Use the helper here too?

> +		if ((mod->module_core) && (mod->core_text_size)) {
> +			set_page_attributes((unsigned long)mod->module_core,
> +						(unsigned long)mod->module_core
> +							+ mod->core_text_size,
> +						set_memory_rw);
> +		}
> +		if ((mod->module_init) && (mod->init_text_size)) {
> +			set_page_attributes((unsigned long)mod->module_init,
> +						(unsigned long)mod->module_init
> +							+ mod->init_text_size,
> +						set_memory_rw);

More unwanted casts...

> +			set_page_attributes((unsigned long)mod->module_core,
> +						(unsigned long)mod->module_core
> +							+ mod->core_text_size,
> +						set_memory_ro);
> +		}
> +		if ((mod->module_init) && (mod->init_text_size)) {
> +			set_page_attributes((unsigned long)mod->module_init,
> +						(unsigned long)mod->module_init
> +							+ mod->init_text_size,
> +						set_memory_ro);

Here, too.

Thanks,
Rusty.

  parent reply	other threads:[~2010-02-01 21:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 16:29 [PATCH V9] RO/NX protection for loadable kernel modules Siarhei Liakh
2010-02-01 21:38 ` James Morris
2010-02-01 21:49 ` Rusty Russell [this message]
2010-02-01 22:48   ` 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=201002020819.55499.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --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=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;
as well as URLs for NNTP newsgroup(s).