From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] powerpc64: Increase SIGSTKSZ and MINSIGSTKSZ
Date: Tue, 13 Dec 2022 00:27:12 -0300 [thread overview]
Message-ID: <644e4c13-67fc-deed-6fb1-2fef13bcd5da@linaro.org> (raw)
In-Reply-To: <04160486-a48e-38c6-cb70-399ed25fa68f@linux.ibm.com>
On 12/12/22 20:31, Paul E Murphy via Libc-alpha wrote:
> On 12/8/22 7:16 PM, Rajalakshmi Srinivasaraghavan via Libc-alpha wrote:
>> This patch increases the value of SIGSTKSZ and MINSIGSTKSZ
>> for powerpc64 similar to the kernel commit
>> 2f82ec19757f58549467db568c56e7dfff8af283 to allow
>> further expansion of the signal stack frame size.
>
> This LGTM. The kernel's commit message is a little confusing to someone who didn't experience the original issue, but make sense once looking through the tree of referenced commits.
Shouldn't powerpc follow x86 to use sysconf (_SC_SIGSTKSZ) as well?
Or this is done unconditionally on kernel without it providing a
AT_MINSIGSTKSZ?
>
>> ---
>> sysdeps/unix/sysv/linux/powerpc/bits/sigstack.h | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/sysdeps/unix/sysv/linux/powerpc/bits/sigstack.h b/sysdeps/unix/sysv/linux/powerpc/bits/sigstack.h
>> index abc87cd7a6..4bff1fe1e7 100644
>> --- a/sysdeps/unix/sysv/linux/powerpc/bits/sigstack.h
>> +++ b/sysdeps/unix/sysv/linux/powerpc/bits/sigstack.h
>> @@ -23,10 +23,15 @@
>> # error "Never include this file directly. Use <signal.h> instead"
>> #endif
>>
>> +#ifdef __powerpc64__
>> +#define MINSIGSTKSZ 8192
>> +#define SIGSTKSZ 32768
>> +#else
>> /* Minimum stack size for a signal handler. */
>> #define MINSIGSTKSZ 4096
>>
>> /* System default stack size. */
>> #define SIGSTKSZ 16384
>> +#endif
>>
>> #endif /* bits/sigstack.h */
next prev parent reply other threads:[~2022-12-13 3:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 1:16 Rajalakshmi Srinivasaraghavan
2022-12-12 23:31 ` Paul E Murphy
2022-12-13 3:27 ` Adhemerval Zanella Netto [this message]
2022-12-13 13:41 ` Rajalakshmi Srinivasaraghavan
2022-12-21 23:58 ` Rajalakshmi Srinivasaraghavan
2022-12-13 16:23 ` Florian Weimer
2022-12-14 16:46 ` Rajalakshmi Srinivasaraghavan
2022-12-15 13:43 ` Tulio Magno Quites Machado Filho
2022-12-15 23:44 ` Rajalakshmi Srinivasaraghavan
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=644e4c13-67fc-deed-6fb1-2fef13bcd5da@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).