All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Irwin <bill.irwin@oracle.com>
To: 'David Gibson' <david@gibson.dropbear.id.au>
Cc: Hugh Dickins <hugh@veritas.com>, Adam Litke <agl@us.ibm.com>,
	"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	'Christoph Lameter' <clameter@sgi.com>,
	'Andrew Morton' <akpm@osdl.org>,
	bill.irwin@oracle.com, linux-mm@kvack.org
Subject: Re: [hugepage] Check for brk() entering a hugepage region
Date: Tue, 14 Nov 2006 15:16:53 -0800	[thread overview]
Message-ID: <20061114231653.GO7919@holomorphy.com> (raw)
In-Reply-To: <20061114040339.GK13060@localhost.localdomain>

On Tue, Nov 14, 2006 at 03:03:39PM +1100, 'David Gibson' wrote:
> Andrew, please apply.  I could have sworn I checked ages ago, and
> thought that sys_brk() eventually called do_mmap_pgoff() which would
> do the necessary checks.  Can't find any evidence of such a change
> though, so either I was just blind at the time, or it happened before
> the changeover to git.
> Unlike mmap(), the codepath for brk() creates a vma without first
> checking that it doesn't touch a region exclusively reserved for
> hugepages.  On powerpc, this can allow it to create a normal page vma
> in a hugepage region, causing oopses and other badness.
> This patch adds a test to prevent this.  With this patch, brk() will
> simply fail if it attempts to move the break into a hugepage reserved
> region.
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Acked-by: William Irwin <wli@holomorphy.com>


-- wli

--
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>

      parent reply	other threads:[~2006-11-14 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14  4:03 [hugepage] Check for brk() entering a hugepage region 'David Gibson'
2006-11-14 15:27 ` Adam Litke
2006-11-14 23:16 ` Bill Irwin [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=20061114231653.GO7919@holomorphy.com \
    --to=bill.irwin@oracle.com \
    --cc=agl@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=hugh@veritas.com \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-mm@kvack.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.