linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: Borislav Petkov <bp@amd64.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, sjhill@mips.com, ralf@linux-mips.org,
	Rob Herring <rob.herring@calxeda.com>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	Nicolas Pitre <nico@linaro.org>
Subject: Re: bugs in page colouring code
Date: Thu, 14 Jun 2012 17:20:38 -0400	[thread overview]
Message-ID: <4FDA55A6.2030706@redhat.com> (raw)
In-Reply-To: <4FDA5413.9080400@linux.intel.com>

On 06/14/2012 05:13 PM, H. Peter Anvin wrote:

> I am much more skeptical to disabling page coloring in the !PF_RANDOMIZE
> case when no address hint is proposed.  I would like to at least try
> running without it, perhaps with a chicken bit in a sysctl.

Agreed, it is hard to imagine a program that passes
address 0 to mmap, yet breaks when it gets a coloured
page address back...

I'll leave that bit of code untouched for now, we can
play with it later.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-06-14 21:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 19:29 bugs in page colouring code Rik van Riel
2012-06-14  8:42 ` Paul Mundt
2012-06-14 12:56   ` Rik van Riel
2012-06-14 10:36 ` Borislav Petkov
2012-06-14 12:57   ` Rik van Riel
2012-06-14 13:20     ` Borislav Petkov
2012-06-14 14:31       ` Ralf Baechle
2012-06-14 20:58     ` H. Peter Anvin
2012-06-14 21:03       ` Rik van Riel
2012-06-14 21:13         ` H. Peter Anvin
2012-06-14 21:20           ` Rik van Riel [this message]
2012-06-14 13:20 ` Russell King - ARM Linux
2012-06-14 14:27   ` Rik van Riel

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=4FDA55A6.2030706@redhat.com \
    --to=riel@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@amd64.org \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nico@linaro.org \
    --cc=ralf@linux-mips.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=rob.herring@calxeda.com \
    --cc=sjhill@mips.com \
    /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).