linux-kernel - Re: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ

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:	Tue, 06 Oct 2015 13:52:24 +0200
From:	Andreas Schwab <schwab@...e.de>
To:	Dave Martin <Dave.Martin@....com>
Cc:	Arnd Bergmann <arnd@...db.de>, catalin.marinas@....com,
	will.deacon@....com, linux-kernel@...r.kernel.org,
	Akhilesh Kumar <akhilesh.k@...sung.com>,
	Manjeet Pawar <manjeet.p@...sung.com>,
	Rohit Thapliyal <r.thapliyal@...sung.com>,
	linux-arm-kernel@...ts.infradead.org, pankaj.m@...sung.com
Subject: Re: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ

Dave Martin <Dave.Martin@....com> writes:

> On Tue, Oct 06, 2015 at 12:59:45PM +0200, Andreas Schwab wrote:
>> Arnd Bergmann <arnd@...db.de> writes:
>> 
>> > I think it makes sense to stick with the traditional definition
>> > of MINSIGSTKSZ == "the minimum amount that you will always need,
>> > add whatever you require yourself" and SIGSTKSZ == "Should be
>> > enough for a couple of function calls".
>> 
>> The python3 testsuite wants to put two signal frames in a SIGSTKSZ
>> stack.
>
> Whether it's valid to expect SIGSTKSZ to be big enough for that is
> debatable.

This is tracked in <https://bugs.python.org/issue22503>.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@...e.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
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/