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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 06 Oct 2015 12:59:45 +0200 From: Andreas Schwab <schwab@...e.de> To: Arnd Bergmann <arnd@...db.de> Cc: Dave Martin <Dave.Martin@....com>, linux-arm-kernel@...ts.infradead.org, catalin.marinas@....com, will.deacon@....com, linux-kernel@...r.kernel.org, Akhilesh Kumar <akhilesh.k@...sung.com>, Rohit Thapliyal <r.thapliyal@...sung.com>, Manjeet Pawar <manjeet.p@...sung.com>, pankaj.m@...sung.com Subject: Re: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ 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. 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/
Powered by blists - more mailing lists