mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [patch] x86: test case for the RODATA config option
Date: Wed, 23 Jan 2008 06:49:05 -0800	[thread overview]
Message-ID: <20080123064905.5d05509a@laptopd505.fenrus.org> (raw)
In-Reply-To: <p731w88nc0p.fsf@crumb.suse.de>

On 23 Jan 2008 10:09:58 +0100
Andi Kleen <andi@firstfloor.org> wrote:

> Arjan van de Ven <arjan@infradead.org> writes:
> 
> > This patch adds a test module for the DEBUG_RODATA config
> > option to make sure change_page_attr() did indeed make
> > "const" data read only.
> 
> The only that this does that is not done pretty much equivalently
> by pageattr-test.c (it just checks G instead of W) is testing the
> kernel text mapping on 64bit. On 32bit it is fully redundant I
> believe.

What it does is check if the rodata marking was succesful. That's more than just checking 
change_page_attr() itself, and basically a reasonably self self-check of mark_rodata_const().


> Testing the kernel mapping might be a good idea, but I would
> suggest adding it to pageattr-test.c

where we move the actual test function... I don't really care. Once pageattr-test.c
is merged I have absolutely no problem moving it there if it's the right place...
(one can argue that it should be in or near the mark_rodata_const() function instead
since it tests that one).
Just like the NX test I wrote yesterday (and will post later today) probably wants to live
somewhere close to the NX code.
 
> Yes I'm sure these basic facts will not stop it from being 
> applied anyways; just wanted to point it out for the benefit
> of the list readers.

Please spare me the bitter, undeserved sarcasm; I don't remember doing anything
to you to deserve that.
-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-01-23 14:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 22:44 Arjan van de Ven
2008-01-23  0:04 ` Ingo Molnar
2008-01-23  1:11 ` Nick Piggin
2008-01-23  5:29   ` Arjan van de Ven
2008-01-23  9:09 ` Andi Kleen
2008-01-23 14:49   ` Arjan van de Ven [this message]
2008-01-23 15:27     ` Andi Kleen
2008-01-23 16:04       ` Arjan van de Ven
2008-01-23 16:54         ` Andi Kleen
2008-01-23 17:49           ` Arjan van de Ven

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=20080123064905.5d05509a@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®