From: schwab@suse.de (Andreas Schwab)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ
Date: Tue, 06 Oct 2015 13:52:24 +0200 [thread overview]
Message-ID: <mvma8rw8b9j.fsf@hawking.suse.de> (raw)
In-Reply-To: <20151006113328.GP6281@e103592.cambridge.arm.com> (Dave Martin's message of "Tue, 6 Oct 2015 12:33:28 +0100")
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>.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Dave Martin <Dave.Martin@arm.com>
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>,
Manjeet Pawar <manjeet.p@samsung.com>,
Rohit Thapliyal <r.thapliyal@samsung.com>,
linux-arm-kernel@lists.infradead.org, pankaj.m@samsung.com
Subject: Re: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ
Date: Tue, 06 Oct 2015 13:52:24 +0200 [thread overview]
Message-ID: <mvma8rw8b9j.fsf@hawking.suse.de> (raw)
In-Reply-To: <20151006113328.GP6281@e103592.cambridge.arm.com> (Dave Martin's message of "Tue, 6 Oct 2015 12:33:28 +0100")
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>.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2015-10-06 11:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 5:35 [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ Manjeet Pawar
2015-10-06 5:35 ` Manjeet Pawar
2015-10-06 7:49 ` Arnd Bergmann
2015-10-06 7:49 ` Arnd Bergmann
2015-10-06 9:37 ` Catalin Marinas
2015-10-06 9:37 ` Catalin Marinas
2015-10-06 10:31 ` Dave Martin
2015-10-06 10:31 ` Dave Martin
2015-10-06 10:51 ` Arnd Bergmann
2015-10-06 10:51 ` Arnd Bergmann
2015-10-06 10:59 ` Andreas Schwab
2015-10-06 10:59 ` Andreas Schwab
2015-10-06 11:33 ` Dave Martin
2015-10-06 11:33 ` Dave Martin
2015-10-06 11:52 ` Andreas Schwab [this message]
2015-10-06 11:52 ` Andreas Schwab
2015-10-06 12:49 ` Dave Martin
2015-10-06 12:49 ` Dave Martin
2015-10-06 11:22 ` Dave Martin
2015-10-06 11:22 ` Dave Martin
2015-10-09 8:41 ` Arnd Bergmann
2015-10-09 8:41 ` Arnd Bergmann
2015-10-12 13:53 ` Dave Martin
2015-10-12 13:53 ` Dave Martin
2015-10-06 10:19 ` Will Deacon
2015-10-06 10:19 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2015-10-09 8:17 Manjeet Pawar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvma8rw8b9j.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.