linux-kernel - Re: [PATCH] Don't allow the stack to grow into hugetlb reserved regions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 26 Jan 2007 14:48:44 -0800
From:	"Ken Chen" <kenchen@...gle.com>
To:	"Hugh Dickins" <hugh@...itas.com>
Cc:	"Adam Litke" <agl@...ibm.com>, "Andrew Morton" <akpm@...l.org>,
	"William Irwin" <wli@...omorphy.com>,
	"David Gibson" <david@...son.dropbear.id.au>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Don't allow the stack to grow into hugetlb reserved regions

On 1/26/07, Hugh Dickins <hugh@...itas.com> wrote:
> Less trivial (and I wonder whether you've come to this from an ia64
> or a powerpc direction): I notice that ia64 has more stringent REGION
> checks in its ia64_do_page_fault, before calling expand_stack or
> expand_upwards.  So on that path, the usual path, I think your
> new check in acct_stack_growth is unnecessary on ia64;

I think you are correct. This appears to affect powerpc only. On ia64,
hugetlb lives in a completely different region and they can never step
into normal stack address space. And for x86, there isn't a thing called
"reserved address space" for hugetlb mapping.

        - Ken
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/