From: Andreas Schwab <schwab@suse.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dave Martin <Dave.Martin@arm.com>,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
Akhilesh Kumar <akhilesh.k@samsung.com>,
Rohit Thapliyal <r.thapliyal@samsung.com>,
Manjeet Pawar <manjeet.p@samsung.com>,
pankaj.m@samsung.com
Subject: Re: [PATCHv2] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ
Date: Tue, 06 Oct 2015 12:59:45 +0200 [thread overview]
Message-ID: <mvmh9m48dpa.fsf@hawking.suse.de> (raw)
In-Reply-To: <5340366.WTVksOGb0G@wuerfel> (Arnd Bergmann's message of "Tue, 06 Oct 2015 12:51:24 +0200")
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.
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 10:59 UTC|newest]
Thread overview: 14+ 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 7:49 ` Arnd Bergmann
2015-10-06 9:37 ` Catalin Marinas
2015-10-06 10:31 ` Dave Martin
2015-10-06 10:51 ` Arnd Bergmann
2015-10-06 10:59 ` Andreas Schwab [this message]
2015-10-06 11:33 ` Dave Martin
2015-10-06 11:52 ` Andreas Schwab
2015-10-06 12:49 ` Dave Martin
2015-10-06 11:22 ` Dave Martin
2015-10-09 8:41 ` Arnd Bergmann
2015-10-12 13:53 ` Dave Martin
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=mvmh9m48dpa.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=Dave.Martin@arm.com \
--cc=akhilesh.k@samsung.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manjeet.p@samsung.com \
--cc=pankaj.m@samsung.com \
--cc=r.thapliyal@samsung.com \
--cc=will.deacon@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox