From: Andrew Morton <akpm@osdl.org>
To: Adam Litke <agl@us.ibm.com>
Cc: linux-mm@kvack.org, david@gibson.dropbear.id.au,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Don't allow the stack to grow into hugetlb reserved regions
Date: Fri, 26 Jan 2007 12:05:54 -0800 [thread overview]
Message-ID: <20070126120554.671b1d6a.akpm@osdl.org> (raw)
In-Reply-To: <20070125214052.22841.33449.stgit@localhost.localdomain>
On Thu, 25 Jan 2007 13:40:52 -0800
Adam Litke <agl@us.ibm.com> wrote:
> When expanding the stack, we don't currently check if the VMA will cross into
> an area of the address space that is reserved for hugetlb pages. Subsequent
> faults on the expanded portion of such a VMA will confuse the low-level MMU
> code, resulting in an OOPS. Check for this.
We prefer not to oops. Is there any reason why this isn't a serious fix, needed
in 2.6.20 and 2.6.19?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@osdl.org>
To: Adam Litke <agl@us.ibm.com>
Cc: linux-mm@kvack.org, david@gibson.dropbear.id.au,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Don't allow the stack to grow into hugetlb reserved regions
Date: Fri, 26 Jan 2007 12:05:54 -0800 [thread overview]
Message-ID: <20070126120554.671b1d6a.akpm@osdl.org> (raw)
In-Reply-To: <20070125214052.22841.33449.stgit@localhost.localdomain>
On Thu, 25 Jan 2007 13:40:52 -0800
Adam Litke <agl@us.ibm.com> wrote:
> When expanding the stack, we don't currently check if the VMA will cross into
> an area of the address space that is reserved for hugetlb pages. Subsequent
> faults on the expanded portion of such a VMA will confuse the low-level MMU
> code, resulting in an OOPS. Check for this.
We prefer not to oops. Is there any reason why this isn't a serious fix, needed
in 2.6.20 and 2.6.19?
--
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>
next prev parent reply other threads:[~2007-01-26 20:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 21:40 [PATCH] Don't allow the stack to grow into hugetlb reserved regions Adam Litke
2007-01-25 21:40 ` Adam Litke
2007-01-26 20:05 ` Andrew Morton [this message]
2007-01-26 20:05 ` Andrew Morton
2007-01-26 21:02 ` Hugh Dickins
2007-01-26 21:02 ` Hugh Dickins
2007-01-26 22:48 ` Ken Chen
2007-01-26 22:48 ` Ken Chen
2007-01-27 9:08 ` Hugh Dickins
2007-01-27 9:08 ` Hugh Dickins
2007-01-28 20:27 ` Ken Chen
2007-01-28 20:27 ` Ken Chen
2007-01-29 17:26 ` Hugh Dickins
2007-01-29 17:26 ` Hugh Dickins
2007-01-29 18:32 ` Ken Chen
2007-01-29 18:32 ` Ken Chen
-- strict thread matches above, loose matches on Subject: below --
2007-01-29 18:34 Adam Litke
2007-01-29 18:34 ` Adam Litke
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=20070126120554.671b1d6a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=agl@us.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--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.