[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb715262-df9e-3e77-6964-80ec4a1c7a24@redhat.com>
Date: Fri, 2 Nov 2018 15:50:11 -0400
From: Waiman Long <longman@...hat.com>
To: Dave Hansen <dave.hansen@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>
Cc: "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] x86/mm/fault: Allow stack access below %rsp
On 11/02/2018 03:44 PM, Dave Hansen wrote:
> On 11/2/18 12:40 PM, Waiman Long wrote:
>> The 64k+ limit check is kind of arbitrary. So the check is now removed
>> to just let expand_stack() decide if a segmentation fault should happen.
> With the 64k check removed, what's the next limit that we bump into? Is
> it just the stack_guard_gap space above the next-lowest VMA?
I think it is both the stack_guard_gap space above the next lowest VMA
and the rlimit(RLIMIT_STACK).
Cheers,
Longman
Powered by blists - more mailing lists