[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez1yZBYPXvqxW8k7uH+jAFkkLK1KNijgPPw+Kp-8gnp-sQ@mail.gmail.com>
Date: Wed, 23 Dec 2020 07:55:20 +0100
From: Jann Horn <jannh@...gle.com>
To: "Chang S. Bae" <chang.seok.bae@...el.com>
Cc: Borislav Petkov <bp@...e.de>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Andy Lutomirski <luto@...nel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
Len Brown <len.brown@...el.com>,
Dave Hansen <dave.hansen@...el.com>,
"H.J. Lu" <hjl.tools@...il.com>, Dave Martin <Dave.Martin@....com>,
Michael Ellerman <mpe@...erman.id.au>,
Tony Luck <tony.luck@...el.com>,
"Ravi V. Shankar" <ravi.v.shankar@...el.com>,
libc-alpha@...rceware.org, linux-arch <linux-arch@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 3/4] x86/signal: Prevent an alternate stack overflow
before a signal delivery
On Wed, Dec 23, 2020 at 2:57 AM Chang S. Bae <chang.seok.bae@...el.com> wrote:
> The kernel pushes data on the userspace stack when entering a signal. If
> using a sigaltstack(), the kernel precisely knows the user stack size.
>
> When the kernel knows that the user stack is too small, avoid the overflow
> and do an immediate SIGSEGV instead.
>
> This overflow is known to occur on systems with large XSAVE state. The
> effort to increase the size typically used for altstacks reduces the
> frequency of these overflows, but this approach is still useful for legacy
> binaries.
>
> Suggested-by: Jann Horn <jannh@...gle.com>
> Signed-off-by: Chang S. Bae <chang.seok.bae@...el.com>
> Reviewed-by: Len Brown <len.brown@...el.com>
> Cc: Jann Horn <jannh@...gle.com>
> Cc: x86@...nel.org
> Cc: linux-kernel@...r.kernel.org
Reviewed-by: Jann Horn <jannh@...gle.com>
Powered by blists - more mailing lists