Re: [PATCH v6 3/6] x86/elf: Support a new ELF aux vector AT_MINSIGSTKSZ

2021-03-10 Thread Bae, Chang Seok
On Mar 10, 2021, at 09:43, Borislav Petkov wrote: > > No, build the docs by doing > > make htmldocs > > and look at the result. > > Btw, you should always look at the result before sending it out. Ah, now I get that. Sorry for my ignorance. I will fix and make sure not missing this check. Th

Re: [PATCH v6 3/6] x86/elf: Support a new ELF aux vector AT_MINSIGSTKSZ

2021-03-10 Thread Borislav Petkov
On Wed, Mar 10, 2021 at 04:34:40PM +, Bae, Chang Seok wrote: > Yeah, right. While this attempts to fix the issue, it involves the ABI change. > Len and I think PATCH5 [1] is rather a backport candidate as it gives a more > reasonable behavior. Yap, patch 5 is more conservative, sure. I guess

Re: [PATCH v6 3/6] x86/elf: Support a new ELF aux vector AT_MINSIGSTKSZ

2021-03-10 Thread Bae, Chang Seok
On Mar 5, 2021, at 02:43, Borislav Petkov wrote: > On Sat, Feb 27, 2021 at 08:59:08AM -0800, Chang S. Bae wrote: >> Historically, signal.h defines MINSIGSTKSZ (2KB) and SIGSTKSZ (8KB), for >> use by all architectures with sigaltstack(2). Over time, the hardware state >> size grew, but these consta

Re: [PATCH v6 3/6] x86/elf: Support a new ELF aux vector AT_MINSIGSTKSZ

2021-03-05 Thread Borislav Petkov
On Sat, Feb 27, 2021 at 08:59:08AM -0800, Chang S. Bae wrote: > Historically, signal.h defines MINSIGSTKSZ (2KB) and SIGSTKSZ (8KB), for > use by all architectures with sigaltstack(2). Over time, the hardware state > size grew, but these constants did not evolve. Today, literal use of these > const

[PATCH v6 3/6] x86/elf: Support a new ELF aux vector AT_MINSIGSTKSZ

2021-02-27 Thread Chang S. Bae
Historically, signal.h defines MINSIGSTKSZ (2KB) and SIGSTKSZ (8KB), for use by all architectures with sigaltstack(2). Over time, the hardware state size grew, but these constants did not evolve. Today, literal use of these constants on several architectures may result in signal stack overflow, and