From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934046AbbJIImV (ORCPT ); Fri, 9 Oct 2015 04:42:21 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:53929 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932346AbbJIImT (ORCPT ); Fri, 9 Oct 2015 04:42:19 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Dave Martin , catalin.marinas@arm.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, Akhilesh Kumar , Manjeet Pawar , Rohit Thapliyal , Andreas Schwab , pankaj.m@samsung.com Subject: Re: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ Date: Fri, 09 Oct 2015 10:41:43 +0200 Message-ID: <5223992.qv9q1k7gFp@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <5340366.WTVksOGb0G@wuerfel> References: <1444109743-8561-1-git-send-email-manjeet.p@samsung.com> <20151006103128.GN6281@e103592.cambridge.arm.com> <5340366.WTVksOGb0G@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:ly7dmtnd3wsfbCU6jaFXAzUNXavFFPKeQR+JU5boqPFAc++UTLo PSBfYPoQOqOM0Tl1ewMZVTmIgj8ymSoKvHYvL2NqnaYGk55cd9CRRhG4K8sxM0Ssytl2xo2 x6j87slTFS/r/UeZJKGxKAZDIbLYDP0kPEKc4za729M5RzX3+5bmyR00QYJ1TjdfeeMdI+Y Q1Tlz+0qqvUpplq+RGh2A== X-UI-Out-Filterresults: notjunk:1;V01:K0:MiLCjLS1TdY=:M5aFd8EYkINdfhoEVIjZH1 SsrVfUPW4PNHJsP4UvfgvAOTWRD8l2ECcxdVlnF31GTH4i1Vl7/0xwV2uWiVmOoNVV+7WN6g6 f4jx54+kBWTeQnYmqVA9D4BCtcFzaD6zqON7npAE9T6kF+zOP06D07x16pKKybW55ajoXW4D+ tLmj/t0oOqpcoO3WWzxicR+v4sYEgH3kCwrfHVL9Dmsx+f5QzW8ULSj3so/svixKmToC75JAz DM+QD1XZmlSmMMpTiFY6nNx0x2dydz6obJ66gwVDDi4q3VlsneH31mrYQZlGGJQIth+XkCE9Z zbsN29l1FZTpBQwyuskz2lHrLIlZZ4rWUKnrfIj8eYZmxmjO6mp2uPPSEBLk4lSNZmDL9eOgO h60kNe/U9OFG5pz28QVDVpbJmC2yI5bQohafQEbVS+BGaKC6W/i8xLQoJIfMGgX7nOK0LOvU8 61lCZp6Ey+6O0W8SbD3npGWh2wems9doGniasVVJ/qmMg/zn0doZc3a3AMzRuSd6oHV3qvi5b l1Tei0SPH3WJJb7isxfyt4sgRxO8NvPGg5yXl8vpp+YyukbwnpF85Xq8hRA6rF5XTJDjGJgay zD+YaOhXSHoZ+hz1zWF5cRls+HRAVsyr5XXnnfeZ8YVC6IP9ahsXb4ERcW5VOFSfqcS31wnTe WZ6qTu/2xDCzyfvWkDaYfMkxf+ZCjrSc75yMibM779u0IH5jnKFqGCF0obWlkM8VbJJ32bVv/ Q2JOvVWxUaS/U0jb Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 06 October 2015 12:51:24 Arnd Bergmann wrote: > > 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". If we want to be conservative > in the kernel, using 8192 and 32768, to stay with the x4 ratio > that everyone else uses would be my first pick, though I'm not > particularly attached to those values. > > On second thought, it really seems to late to make up our minds about the size now that glibc has already established 5KB as the minimum size. If we set it to 8KB/32KB, not just the testcase but real applications would start failing when they use the 5KB constant from glibc. Arnd