From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751906AbbJFMtH (ORCPT <rfc822;w@1wt.eu>);
	Tue, 6 Oct 2015 08:49:07 -0400
Received: from eu-smtp-delivery-143.mimecast.com ([207.82.80.143]:54812 "EHLO
	eu-smtp-delivery-143.mimecast.com" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1750810AbbJFMtG convert rfc822-to-8bit
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 6 Oct 2015 08:49:06 -0400
Date: Tue, 6 Oct 2015 13:49:02 +0100
From: Dave Martin <Dave.Martin@arm.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Arnd Bergmann <arnd@arndb.de>, catalin.marinas@arm.com,
        will.deacon@arm.com, linux-kernel@vger.kernel.org,
        Akhilesh Kumar <akhilesh.k@samsung.com>,
        linux-arm-kernel@lists.infradead.org,
        Rohit Thapliyal <r.thapliyal@samsung.com>,
        Manjeet Pawar <manjeet.p@samsung.com>, pankaj.m@samsung.com
Subject: Re: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ
Message-ID: <20151006124902.GQ6281@e103592.cambridge.arm.com>
References: <1444109743-8561-1-git-send-email-manjeet.p@samsung.com>
 <5022096.8QRzW0l3EJ@wuerfel>
 <20151006103128.GN6281@e103592.cambridge.arm.com>
 <5340366.WTVksOGb0G@wuerfel>
 <mvmh9m48dpa.fsf@hawking.suse.de>
 <20151006113328.GP6281@e103592.cambridge.arm.com>
 <mvma8rw8b9j.fsf@hawking.suse.de>
MIME-Version: 1.0
In-Reply-To: <mvma8rw8b9j.fsf@hawking.suse.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-OriginalArrivalTime: 06 Oct 2015 12:49:02.0888 (UTC) FILETIME=[60DDF280:01D10035]
X-MC-Unique: yXz8qr_QTe6BBLfIAWFKWQ-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Oct 06, 2015 at 01:52:24PM +0200, Andreas Schwab wrote:
> Dave Martin <Dave.Martin@arm.com> writes:
> 
> > On Tue, Oct 06, 2015 at 12:59:45PM +0200, Andreas Schwab wrote:
> >> Arnd Bergmann <arnd@arndb.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>.

Fair enough...

Cheers
---Dave